Skip to content

Files

Latest commit

Jan 3, 2013
78a5e73 · Jan 3, 2013

History

History

contrib

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Jan 1, 2013
Nov 18, 2012
Jan 1, 2013
Oct 12, 2011
Jul 5, 2012
Oct 12, 2011
Jul 5, 2012
Oct 11, 2012
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Oct 12, 2011
Jan 1, 2013
Jan 1, 2013
Oct 1, 2012
Oct 12, 2011
Jul 16, 2012
Jan 1, 2013
Oct 12, 2011
Aug 30, 2012
Oct 2, 2012
Jan 1, 2013
Jan 1, 2013
Oct 12, 2012
Aug 30, 2012
Oct 12, 2011
Oct 12, 2012
Jan 1, 2013
Nov 30, 2012
Nov 30, 2012
Aug 20, 2012
Jan 3, 2013
Jan 1, 2013
Jan 1, 2013
Jun 10, 2012
Oct 12, 2011
Dec 5, 2012
Oct 11, 2012
Jan 1, 2013
Jun 10, 2012
Apr 24, 2012
Jun 13, 2012
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Jan 1, 2013
Dec 6, 2012
Aug 30, 2012
Dec 6, 2012
Apr 14, 2012
Sep 20, 2010
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.