postgresql/contrib
Peter Eisentraut bb7520cc26 Make documentation of --help and --version options more consistent
Before, some places didn't document the short options (-? and -V),
some documented both, some documented nothing, and they were listed in
various orders.  Now this is hopefully more consistent and complete.
2012-06-18 02:46:59 +03:00
..
adminpack
auth_delay
auto_explain Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
btree_gin
btree_gist
chkpass
citext Fix contrib/citext's upgrade script to handle array and domain cases. 2012-05-11 15:22:30 -04:00
cube
dblink Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
dict_int
dict_xsyn
dummy_seclabel
earthdistance
file_fdw Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
fuzzystrmatch Even more duplicate word removal, in the spirit of the season 2012-05-02 20:56:03 +03:00
hstore Lots of doc corrections. 2012-04-23 22:43:09 -04:00
intagg
intarray Add const qualifiers where they are accidentally cast away 2012-02-28 12:42:08 +02:00
isn
lo
ltree Add const qualifiers where they are accidentally cast away 2012-02-28 12:42:08 +02:00
oid2name Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
pageinspect
passwordcheck
pg_archivecleanup Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
pg_buffercache
pg_freespacemap
pg_standby Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
pg_stat_statements Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
pg_test_fsync Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
pg_test_timing Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
pg_trgm Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
pg_upgrade Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
pg_upgrade_support
pgbench Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
pgcrypto Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
pgrowlocks
pgstattuple Remove RELKIND_UNCATALOGED. 2012-06-14 09:47:30 -04:00
seg
sepgsql Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
spi Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
sslinfo Lots of doc corrections. 2012-04-23 22:43:09 -04:00
start-scripts Support Linux's oom_score_adj API as well as the older oom_adj API. 2012-06-13 15:35:52 -04:00
tablefunc
tcn
test_parser
tsearch2
unaccent Fix some typos 2012-04-22 19:23:47 +03:00
uuid-ossp
vacuumlo Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
xml2 Run pgindent on 9.2 source tree in preparation for first 9.3 2012-06-10 15:20:04 -04:00
contrib-global.mk
Makefile pg_test_timing utility, to measure clock monotonicity and timing cost. 2012-03-27 16:14:00 -04:00
README Update contrib/README 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.