postgresql/contrib
Peter Eisentraut 081ca7a0d1 Tweak contrib --help output to match common style
Placeholders such as OPTION are typically kept in singular.
2012-05-08 21:55:05 +03:00
..
adminpack Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
auth_delay
auto_explain Fix auto-explain JSON output to be valid JSON. 2012-02-13 08:22:15 -05:00
btree_gin
btree_gist
chkpass
citext
cube
dblink Another typographical correction. 2012-04-24 08:15:45 -04:00
dict_int Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
dict_xsyn Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
dummy_seclabel Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
earthdistance
file_fdw Revise parameterized-path mechanism to fix assorted issues. 2012-04-19 15:53:47 -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 Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
lo
ltree Add const qualifiers where they are accidentally cast away 2012-02-28 12:42:08 +02:00
oid2name Tweak contrib --help output to match common style 2012-05-08 21:55:05 +03:00
pageinspect Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
passwordcheck Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
pg_archivecleanup Allow pg_archivecleanup to strip optional file extensions. 2012-04-05 14:18:42 -04:00
pg_buffercache
pg_freespacemap
pg_standby
pg_stat_statements Rename I/O timing statistics columns to blk_read_time and blk_write_time. 2012-04-29 18:13:33 -04:00
pg_test_fsync Fix pg_test_fsync Win32 problems reported by the build farm; add 2012-02-15 07:10:48 -05:00
pg_test_timing pg_test_timing: Lame hack to work around compiler warning. 2012-03-30 08:17:54 -04:00
pg_trgm
pg_upgrade Tweak contrib --help output to match common style 2012-05-08 21:55:05 +03:00
pg_upgrade_support Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
pgbench Tweak contrib --help output to match common style 2012-05-08 21:55:05 +03:00
pgcrypto Fix misleading comments 2012-05-08 19:35:22 +03:00
pgrowlocks
pgstattuple pgstattuple: Use a BufferAccessStrategy object to avoid cache-trashing. 2012-03-13 09:51:45 -04:00
seg
sepgsql More duplicate word removal. 2012-05-02 09:28:16 -04:00
spi
sslinfo Lots of doc corrections. 2012-04-23 22:43:09 -04:00
start-scripts
tablefunc Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
tcn Triggered change notifications. 2012-01-19 23:15:15 -05:00
test_parser Fix one-byte buffer overrun in contrib/test_parser. 2012-01-09 19:56:27 -05:00
tsearch2 Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
unaccent Fix some typos 2012-04-22 19:23:47 +03:00
uuid-ossp Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
vacuumlo Improve the -l (limit) option recently added to contrib/vacuumlo. 2012-03-20 19:05:44 -04:00
xml2
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.