Committed to PostgreSQL on Sunday was support for JSONB, a structed format for storing JSON. "The new format accepts exactly the same data as the json type. However, it is stored in a format that does not require reparsing the orgiginal text in order to process it, making it much more suitable for indexing and other operations. Insignificant whitespace is discarded, and the order of object keys is not preserved. Neither are duplicate object keys kept - the later value for a given key is the only one stored."
Oleg Bartunov, one of the developers working on this code, wrote a blog post adding, "I hope all database people understand, what that project mean for PostgreSQL - 99.9% percent of projects don't need MongoDB and could be nicely implemented in relational model. Now, PostgreSQL (AFAIK, the first considerable RDBMS) introduced the real support for semi-structured data, which are common in nowaday world."
Phoronix reader Thom Brown wrote into Phoronix to share the news of this binary JSON data type support being added to the PostgreSQL database server. Thom explained, "the jsonb data type and related index operator classes were committed to PostgreSQL. This effectively puts MongoDB-like functionality into PostgreSQL with speeds that can meet or exceed MongoDB, and much more flexible indexes." Thom also shared some early benchmark figures with us via his Google+ page:
table sizeFor database developers interested in more information on this work, there's also PDF slides from last year's PostgreSQL European conference concerning this work. This JSONB support will be found in the upcoming PostgreSQL 9.4 release. Earlier this month PostgreSQL also picked up support for logical decoding.
jsonb: 1375MB (4% increase)
JHO: 283MB (55% decrease)
size of targeted index on a single key
JHO: 58MB (26% decrease)
speed (producing a count based on the search for a particular nested value)
JHO: 1.111ms (94% decrease)
Table size is slightly larger with a 4% increase in size, but the index is much smaller and much much faster!