Heikki Linnakangas 36a35c550a Compress GIN posting lists, for smaller index size.
GIN posting lists are now encoded using varbyte-encoding, which allows them
to fit in much smaller space than the straight ItemPointer array format used
before. The new encoding is used for both the lists stored in-line in entry
tree items, and in posting tree leaf pages.

To maintain backwards-compatibility and keep pg_upgrade working, the code
can still read old-style pages and tuples. Posting tree leaf pages in the
new format are flagged with GIN_COMPRESSED flag, to distinguish old and new
format pages. Likewise, entry tree tuples in the new format have a
GIN_ITUP_COMPRESSED flag set in a bit that was previously unused.

This patch bumps GIN_CURRENT_VERSION from 1 to 2. New indexes created with
version 9.4 will therefore have version number 2 in the metapage, while old
pg_upgraded indexes will have version 1. The code treats them the same, but
it might be come handy in the future, if we want to drop support for the
uncompressed format.

Alexander Korotkov and me. Reviewed by Tomas Vondra and Amit Langote.
2014-01-22 19:20:58 +02:00
..
2014-01-07 16:05:30 -05: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-07 16:05:30 -05:00
2014-01-06 21:30:26 -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-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
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-15 21:14:28 -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
2012-04-14 09:29:54 +03: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 "gmake all" and "gmake
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.