postgresql/contrib
Bruce Momjian fbcfa90bb8 Fix pg_upgrade file share violation on Windows created by the commit
4741e9afb9.  This was done by adding an
optional second log file parameter to exec_prog(), and closing and
reopening the log file between system() calls.

Backpatch to 9.2.
2012-08-07 13:10:44 -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 Reduce messages about implicit indexes and sequences to DEBUG1. 2012-07-04 20:35:29 -04:00
chkpass
citext Reduce messages about implicit indexes and sequences to DEBUG1. 2012-07-04 20:35:29 -04:00
cube Replace int2/int4 in C code with int16/int32 2012-06-25 01:51:46 +03:00
dblink Replace libpq's "row processor" API with a "single row" mode. 2012-08-02 13:10:30 -04:00
dict_int
dict_xsyn
dummy_seclabel
earthdistance
file_fdw Skip text->binary conversion of unnecessary columns in contrib/file_fdw. 2012-07-12 16:26:59 -04:00
fuzzystrmatch
hstore Remove unreachable code 2012-07-16 22:15:03 +03:00
intagg
intarray Remove unreachable code 2012-07-16 22:15:03 +03:00
isn
lo
ltree Remove unreachable code 2012-07-16 22:15:03 +03:00
oid2name Make oid2name, pgbench, and vacuumlo set fallback_application_name. 2012-07-04 15:39:33 -04: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 Make new event trigger facility actually do something. 2012-07-20 11:39:01 -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 Fix pg_upgrade file share violation on Windows created by the commit 2012-08-07 13:10:44 -04:00
pg_upgrade_support
pgbench Make pgbench vacuum before building indexes. 2012-07-23 14:42:35 -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 Reduce messages about implicit indexes and sequences to DEBUG1. 2012-07-04 20:35:29 -04:00
seg Run newly-configured perltidy script on Perl files. 2012-07-04 21:47:49 -04:00
sepgsql Reduce messages about implicit indexes and sequences to DEBUG1. 2012-07-04 20:35:29 -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 Reduce messages about implicit indexes and sequences to DEBUG1. 2012-07-04 20:35:29 -04:00
tcn
test_parser
tsearch2
unaccent
uuid-ossp
vacuumlo Make oid2name, pgbench, and vacuumlo set fallback_application_name. 2012-07-04 15:39:33 -04: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.