postgresql/contrib
Alvaro Herrera 4741e9afb9 Make the pg_upgrade log files contain actual commands
Now the log file not only contains the output from commands executed by
system(), but also what command it was in the first place.  This
arrangement makes debugging a lot simpler.
2012-06-29 11:39:11 -04: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 Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
chkpass
citext Fix contrib/citext's upgrade script to handle array and domain cases. 2012-05-11 15:22:30 -04:00
cube Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
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
hstore Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
intagg
intarray Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
isn
lo
ltree Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
oid2name Make documentation of --help and --version options more consistent 2012-06-18 02:46:59 +03:00
pageinspect Replace XLogRecPtr struct with a 64-bit integer. 2012-06-24 19:19:45 +03:00
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 Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
pg_upgrade Make the pg_upgrade log files contain actual commands 2012-06-29 11:39:11 -04:00
pg_upgrade_support
pgbench Make pgbench -i emit only one-tenth as many status messages. 2012-06-22 09:03:25 -04: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
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
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
README

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.