PostgreSQL 10.2 Released
postgresql.org
postgresql.org
While this looks like an important update, note that it's not a new feature release.
Josh Berkus discusses this here:
http://www.databasesoup.com/2016/05/changing-postgresql-vers...
I'm astounded that they support those architectures
I work on PG, and I'm regularly astounded too...
As long as the compilers are new enough, the burden isn't too high though. Previously it prevented us from using atomics for some concurrency optimized things, but now we've an atomics implementation that, at compile time, falls back to a spinlock backed atomics implementation. Slightly complicated by the fact that we don't even have a hard dep on a spinlock implementation, falling back to semaphores :)
Ah. Fun.
But seriously, the thing that hurts more is that we only require a C89 compiler :/
Indeed. For a glimpse for the non-PG-hackers (like me), there's an ongoing attempt discussed in the PG-hackers mailing list to use stdbool.h.
In C99
(bool)256 == 1
but on systems which emulate bool with, e.g., an 8-bit unsigned char then (bool)256 == 0TIL PL/pgSQL exists so I googled it. In the page for porting from Oracle PL/SQL:
>Instead of packages, use schemas to organize your functions into groups.
Does anyone know if there are plans to introduce packages in Postgres? Doesn't putting function in different schemas mean you have to grant select/update permissions to the schemas that talk to other schemas?
*edit:formatting
In Pg, schemas don't talk to schemas. When a function is run, it runs with the privilege level of either the user that called it, or the user that defined it.
(disclaimer: my employer (but open source))
DBeaver is another great alternative.