Skip to content

Files

Latest commit

Jan 12, 2017
da0dbea · Jan 12, 2017

History

History

contrib

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Nov 29, 2016
Nov 29, 2016
Dec 12, 2016
Nov 29, 2016
Nov 29, 2016
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Nov 3, 2016
Jan 3, 2017
Jan 3, 2017
Nov 29, 2016
Oct 4, 2016
Oct 4, 2016
Jun 10, 2016
Jan 3, 2017
Jan 3, 2017
Jun 7, 2016
Nov 29, 2016
Oct 4, 2016
Aug 30, 2016
Jan 3, 2017
Jan 3, 2017
Sep 29, 2016
Jun 9, 2016
Jan 3, 2017
Aug 30, 2016
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Dec 12, 2016
Jun 24, 2016
Jan 3, 2017
Jan 6, 2017
Jan 5, 2017
Jan 3, 2017
Nov 8, 2016
Sep 15, 2016
Jan 12, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Jan 3, 2017
Nov 7, 2016
Apr 1, 2016
Feb 12, 2014
Feb 27, 2016
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.