Andrew Dunstan d9134d0a35 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.

Authors: Oleg Bartunov,  Teodor Sigaev, Peter Geoghegan and Andrew Dunstan.
Review: Andres Freund
2014-03-23 16:40:19 -04:00
..
2014-01-07 16:05:30 -05:00
2013-05-29 16:58:43 -04:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-13 15:43:29 +02:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-02-27 21:52:21 -05:00
2014-03-17 20:47:28 +09:00
2014-01-07 16:05:30 -05:00
2013-10-13 00:09:18 -04:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-01-07 16:05:30 -05:00
2014-03-03 16:32:18 -05:00

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.