Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PostgreSQL 9.3 Beta 1 Released

postgresql.org

Post reply on HN
Print view View original

21–30 of 118 posts

Re: PostgreSQL 9.3 Beta 1 Released

#21

Post by zapov »

tiwazz wrote: post #17
alberth wrote: post #7

Earlier quoted context omitted.

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

I don't believe hstore supports nested structures, which would make it less than a drop in replacement for many NoSQL use cases. Native JSON support should fix that though, so good news everyone! http://www.postgresql.org/docs/devel/static/functions-json.h...

Postgres supports native nested structures. Well, as long as your structures are not circular. JSON everywhere is really a bad choice for most data structures. It's like having no structure at all.

Re: PostgreSQL 9.3 Beta 1 Released

#22

Post by jeltz »

simonw wrote: post #13

"Indexed regular expression search" How does that work from a computer science point of view? UPDATE: Found this talk about it from PGCon last year: http://lanyrd.com/2012/pgcon/schdzf/

It is an extension of how 9.2 can use trigram indexes for LIKE '%foo%' searches.

Re: PostgreSQL 9.3 Beta 1 Released

#23

Post by masklinn »

jeltz wrote: post #19
masklinn wrote: post #11

Earlier quoted context omitted.

the json support is fairly recent and doesn't support operating directly on the data yet (e.g. you have to create functional indexes through plv8js and you can't directly query on the document's content as you can with array, xml or hstore columns)

PostgreSQL 9.3 adds functions for accessing JSON data without having to use plv8js.

Yeah but since it's just being added, it precludes "NoSQL guys" having built upon it, which is the original complaint.

Re: PostgreSQL 9.3 Beta 1 Released

#24

Post by masklinn »

zapov wrote: post #21
tiwazz wrote: post #17

Earlier quoted context omitted.

I don't believe hstore supports nested structures, which would make it less than a drop in replacement for many NoSQL use cases. Native JSON support should fix that though, so good news everyone! http://www.postgresql.org/docs/devel/static/functions-json.h...

Postgres supports native nested structures. Well, as long as your structures are not circular. JSON everywhere is really a bad choice for most data structures. It's like having no structure at all.

Which is pretty much what you want to build a schemaless nosql-on-postgres.

Also, Posgres already has hstore (already mentioned) and XML columns, which are schemaless and "unstructured".

Re: PostgreSQL 9.3 Beta 1 Released

#25

Post by snaky »

gbog wrote: post #6
zapov wrote: 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?

If there would be HandlerSocket or similar, yes.

Re: PostgreSQL 9.3 Beta 1 Released

#27

Post by btown »

masklinn wrote: post #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 t…

Where would one find out if anyone is working on a patch for ActiveRecord?

Re: PostgreSQL 9.3 Beta 1 Released

#28

Post by masklinn »

Refefer wrote: post #20

Materialized Views! Well, sort of; it appears they don't automatically refresh when data has been updated in the underlying tables ala Oracle's implementation, but this gets you rather close.

FWIW, since Posgtres has hard version cycles (6 months I believe?) the point was to have a working base out and about, future versions will likely add auto-update:

> This is a minimal implementation, but should still be useful in many cases. Currently data is only populated "on demand" by the CREATE MATERIALIZED VIEW and REFRESH MATERIALIZED VIEW statements.

> It is expected that future releases will add incremental updates with various timings, and that a more refined concept of defining what is "fresh" data will be developed. At some point it may even be possible to have queries use a materialized in place of references to underlying tables, but that requires the other above-mentioned features to be working first.

http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;...

Re: PostgreSQL 9.3 Beta 1 Released

#29

Post by snaky »

zapov wrote: 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…

But now we can have both - PostgreSQL with all the batteries + (as just one of that batteries) any additional NoSQL backend using http://blog.endpoint.com/2013/05/foreign-data-wrappers.html

Re: PostgreSQL 9.3 Beta 1 Released

#30

Post by masklinn »

orf wrote: post #26

The "User-defined background workers for automating database tasks" feature sounds very interesting: http://www.postgresql.org/docs/9.3/static/bgworker.html I wonder if it would be possible to plug a python/node interpreter into that.

> I wonder if it would be possible to plug a python/node interpreter into that.

Looks like it just takes a C function pointer, if you can call whatever from C you're done (you can embed Python, no idea for Node).

Looks like this is mostly for postgres extension modules though (e.g. foreign data wrappers), it's not for applications (postgres clients).

Post reply on HN