From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Introduce jsonb, a structured format for storing json. |
Date: | 2014-03-23 22:18:42 |
Message-ID: | CAA-aLv7gOCBrUbAUb1sbyp9iAWx==vf-jkfYqS3wOB=iTnMCMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 23 March 2014 21:17, Andrew Dunstan <andrew(at)dunslane(dot)net> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-03-23 22:26:25 | pgsql: Fix mis-spelling in jsonb docs. |
Previous Message | Andrew Dunstan | 2014-03-23 21:17:51 | pgsql: Introduce jsonb, a structured format for storing json. |