If, like me a moment ago, you have no idea what jsonb is; see here for a full explanation <a href="http://www.postgresql.org/message-id/E1WRpmB-0002et-MT@gemulon.postgresql.org" rel="nofollow">http://www.postgresql.org/message-id/E1WRpmB-0002et-MT@gemul...</a><p>tl;dr storing json in a way that doesn't mean repeatedly parsing it to make updates
PostgreSQL was already able to compete with Oracle's RDBMS and Microsoft's SQL Server but could soon supplant Mongo for most jobs.<p>It's great to know that the only required storage components nowadays could be PG and ElasticSearch (as PG's full-text search can't compete with ES), and that the former is a no-brainer to setup (on top of AWS, Rackspace, etc.) or cheap to acquire (with Heroku Postgres for example).<p>Good job !
For those interested, the online documentation for the development version of PostgreSQL has been rebuilt and contains documentation about the new feature:<p><a href="http://www.postgresql.org/docs/devel/static/datatype-json.html" rel="nofollow">http://www.postgresql.org/docs/devel/static/datatype-json.ht...</a>
Pardon if this is a little ignorant - I haven't done a lot of SQL before, so <a href="http://www.postgresql.org/docs/9.3/static/functions-json.html" rel="nofollow">http://www.postgresql.org/docs/9.3/static/functions-json.htm...</a> isn't that obvious to me - but:<p>Does this mean I can do Mongo-style queries, retrieving a set of documents which match particular key: value criteria, using PostgreSQL?
<i>> Jsonb has several missing useful features (from nested hstore), but that could be added later as an extension.</i><p>Which are those missing useful features?
Slightly off-topic, does anyone know if there is progress being made on the proposed HTTP API for PostgreSQL?(<a href="http://wiki.postgresql.org/wiki/HTTP_API" rel="nofollow">http://wiki.postgresql.org/wiki/HTTP_API</a>)
What does this binary format actually look like on disk? Is this documented anywhere other than in the code that reads and writes it?<p>I do remember a description of it in some slides a few months back, but i can't find them now.
I only hope it won't be too long before various "drivers" and frameworks start supporting it, otherwise the acceptance rate will be too low. And Jsonb deserves to be accepted as fast as possible.
Can anyone comment on the storage overhead of JSONB key names? One of the worst things about MongoDB's BSON format is that 8M instances of the following record:<p>{
"user": "test",
"isValid": true
}<p>will at a minimum cost 8M * (4 + 7) simply due to field name overhead. MongoDB isn't smart enough to alias common field names, and this has remained as one of its biggest problems.<p><a href="https://jira.mongodb.org/browse/SERVER-863" rel="nofollow">https://jira.mongodb.org/browse/SERVER-863</a>
Is there a trend of making verbs reflexive among developers/managers? I've seen "product X has released", "patch Y has applied", and a lot of similar phrases which I'm still having trouble parsing. When I saw the title I thought "has committed what?"
Does the JSON type still have a set of use cases as well or is it just obsolete now? If I was writing large quantities of json documents to a table, and I didn't need tag indexing or targeted updating, would using the JSON type be faster than JSONB?