Skip to content

Files

Latest commit

Feb 16, 2019
faee6fa · Feb 16, 2019

History

History

contrib

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Jan 2, 2019
Feb 6, 2019
Jan 2, 2019
Jan 2, 2019
Feb 15, 2019
Jul 29, 2018
Feb 13, 2019
Nov 23, 2018
Feb 13, 2019
Jan 21, 2019
Jan 2, 2019
Jan 2, 2019
Jul 29, 2018
Feb 7, 2019
Jan 2, 2019
Jan 26, 2019
Oct 18, 2018
Sep 16, 2018
Jun 10, 2016
Feb 16, 2019
Jan 2, 2019
Oct 18, 2018
Oct 5, 2018
Sep 15, 2017
Feb 16, 2019
Sep 16, 2018
Jan 19, 2019
Feb 4, 2019
Jan 2, 2019
Nov 21, 2018
Jan 21, 2019
Jan 21, 2019
Jan 19, 2019
Feb 16, 2019
Feb 16, 2019
Jan 22, 2019
Feb 16, 2019
Jan 22, 2019
Jan 22, 2019
Feb 16, 2019
Feb 13, 2019
Jan 22, 2019
Oct 11, 2018
Jun 21, 2017
Nov 17, 2017
Jan 2, 2019
Jan 2, 2019
Feb 12, 2019
Jan 29, 2019
Jan 29, 2019
Feb 1, 2019
Jan 2, 2019
Jan 19, 2019
Jun 21, 2017
Apr 3, 2018
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.