postgresql/contrib
Robert Haas cacbdd7810 Use appendStringInfoString instead of appendStringInfo where possible.
This shaves a few cycles, and generally seems like good programming
practice.

David Rowley
2013-10-31 10:55:59 -04:00
..
adminpack Add use of asprintf() 2013-10-13 00:09:18 -04:00
auth_delay
auto_explain
btree_gin
btree_gist pgindent run for release 9.3 2013-05-29 16:58:43 -04:00
chkpass
citext Add record_image_ops opclass for matview concurrent refresh. 2013-10-09 14:26:09 -05:00
cube Use appendStringInfoString instead of appendStringInfo where possible. 2013-10-31 10:55:59 -04:00
dblink Use appendStringInfoString instead of appendStringInfo where possible. 2013-10-31 10:55:59 -04:00
dict_int
dict_xsyn
dummy_seclabel
earthdistance
file_fdw pgindent run for release 9.3 2013-05-29 16:58:43 -04:00
fuzzystrmatch fuzzystrmatch: replace broken link in C comment 2013-09-10 21:34:01 -04:00
hstore Return valid json when converting an empty hstore. 2013-10-17 11:12:48 -04:00
intagg
intarray intarray: return empty zero-dimensional array for an empty array 2013-09-07 11:44:33 -04:00
isn
lo
ltree
oid2name Replace pg_asprintf() with psprintf(). 2013-10-22 19:40:26 -04:00
pageinspect Fix typo in update scripts for some contrib modules. 2013-07-19 04:13:01 +09:00
passwordcheck
pg_archivecleanup pgindent run for release 9.3 2013-05-29 16:58:43 -04:00
pg_buffercache
pg_freespacemap
pg_standby pgindent run for release 9.3 2013-05-29 16:58:43 -04:00
pg_stat_statements Fix typo in update scripts for some contrib modules. 2013-07-19 04:13:01 +09:00
pg_test_fsync pg_test_fsync: expand ops/sec display 2013-08-02 00:45:19 -04:00
pg_test_timing Remove undocumented -h (help) option 2013-07-01 12:40:33 -04:00
pg_trgm Use appendStringInfoString instead of appendStringInfo where possible. 2013-10-31 10:55:59 -04:00
pg_upgrade Work around NetBSD shell issue in pg_upgrade test script. 2013-10-28 11:45:50 -04:00
pg_upgrade_support
pg_xlogdump Remove broken PGXS code for pg_xlogdump 2013-10-01 17:36:15 -03:00
pgbench pgbench: Comment on thread timing hazards. 2013-10-06 09:57:26 -04:00
pgcrypto pgindent run for release 9.3 2013-05-29 16:58:43 -04:00
pgrowlocks pgrowlocks: Use GetActiveSnapshot() rather than SnapshotNow. 2013-07-22 16:21:14 -04:00
pgstattuple pgstattuple: Use SnapshotDirty, not SnapshotNow. 2013-07-25 16:21:13 -04:00
postgres_fdw Use appendStringInfoString instead of appendStringInfo where possible. 2013-10-31 10:55:59 -04:00
seg Fix contrib/cube and contrib/seg to build with bison 3.0. 2013-07-29 10:42:37 -04:00
sepgsql Use an MVCC snapshot, rather than SnapshotNow, for catalog scans. 2013-07-02 09:47:01 -04:00
spi Add use of asprintf() 2013-10-13 00:09:18 -04:00
sslinfo
start-scripts Remove dead URL mention in OSX startup script 2013-09-04 17:04:33 -04:00
tablefunc Use appendStringInfoString instead of appendStringInfo where possible. 2013-10-31 10:55:59 -04:00
tcn
test_parser
tsearch2
unaccent unaccent: mark unaccent() functions as immutable 2013-10-08 12:20:36 -04:00
uuid-ossp
vacuumlo vacuumlo: Use a cursor to limit client-side memory usage. 2013-07-15 10:51:27 -04:00
worker_spi Fix thinko in worker_spi, count(*) returns a bigint. Thanks RhodiumToad 2013-09-03 13:27:34 +01:00
xml2
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.