On 23 March 2014 21:17, Andrew Dunstan <[email protected]> wrote:
> Introduce jsonb, a structured 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.
>
> The new type has all the functions and operators that the json type has,
> with the exception of the json generation functions (to_json, json_agg etc.)
> and with identical semantics. In addition, there are operator classes for
> hash and btree indexing, and two classes for GIN indexing, that have no
> equivalent in the json type.
>
> This feature grew out of previous work by Oleg Bartunov and Teodor Sigaev, 
> which
> was intended to provide similar facilities to a nested hstore type, but which
> in the end proved to have some significant compatibility issues.

Only noticed the one typo during a skim read...

In doc/src/sgml/json.sgml:

s/aquired/acquired/

-- 
Thom


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

Reply via email to