Live data from Hacker News

PostgreSQL 9.3 Beta 1 Released

postgresql.org

1–10 of 118 posts

Re: PostgreSQL 9.3 Beta 1 Released

#5
Postgres type system is so much better than any other RDBMS that it's a shame NoSQL guys didn't spend more time building on top of it. While their optimizer could use some work here and there it's improving all the time.

We are doing some pretty obscure stuff to it and it's serving us well. Oracle on the other hand requires so much attention and special handling with it's type system, that if there were an alternative, I wouldn't even bother with it.

Re: PostgreSQL 9.3 Beta 1 Released

#6
post #5

Postgres type system is so much better than any other RDBMS that it's a shame NoSQL guys didn't spend more time building on top of it. While their optimizer could use some work here and there it's improving all the time. We are doing some pretty obscure stuff to it and it's serving us well. Oracle on the other hand requires so much attention and special handling with it's type system, that if there were an alternativ…

It seems you could easily get a nosql postgres if you limit yourself to one table with two columns (id, json). Snark apart, it would work quite ok, no?

Re: PostgreSQL 9.3 Beta 1 Released

#7
post #5

Postgres type system is so much better than any other RDBMS that it's a shame NoSQL guys didn't spend more time building on top of it. While their optimizer could use some work here and there it's improving all the time. We are doing some pretty obscure stuff to it and it's serving us well. Oracle on the other hand requires so much attention and special handling with it's type system, that if there were an alternativ…

HStore [1] is NoSQL plugin for Postgres. Works great. Been available for a long time too.

[1] http://www.postgresql.org/docs/9.0/static/hstore.html

Re: PostgreSQL 9.3 Beta 1 Released

#9
The short log is missing one of the most important and awesome new feature to application writers: a bunch of new PQresultErrorFields[0] on constraint failure, providing access to (context-dependent) the raw schema name, table name, column name, constraint name and datatype involved.

Previously these remained locked into the database and to get programmatically-useable info (for logging, better error messages or to translate in terms of e.g. your ORM) you had to parse error messages which were potentially localized and usually lacked half the necessary information.

And even better, for python developers, psycopg2 already supports these fields[1][2]

[0] http://www.postgresql.org/docs/devel/static/libpq-exec.html#...

[1] http://psycopg.lighthouseapp.com/projects/62710/tickets/149

[2] http://initd.org/psycopg/docs/extensions.html#psycopg2.exten...

Re: PostgreSQL 9.3 Beta 1 Released

#10
post #8

for a more in depth list of changes / new features look at release note[1] and the wiki 9.3Beta1 page[2] [1] http://www.postgresql.org/docs/devel/static/release-9-3.html [2] http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9...

Materialised views! Damn, I really could have used that a year and a bit ago..
Post reply on HN