postgresql/contrib
Robert Haas ccd8f97922 postgres_fdw: Consider requesting sorted data so we can do a merge join.
When use_remote_estimate is enabled, consider adding ORDER BY to the
query we sending to the remote server so that we can use that ordered
data for a merge join.  Commit f18c944b61
arranges to push down the query pathkeys, which seems like the case
mostly likely to be a win, but testing shows this can sometimes win,
too.

For a regular table, we know which indexes are present and therefore
test whether the ordering provided by each such index is useful.  Here,
we take the opposite approach: guess what orderings would be useful if
they could be generated cheaply, and then ask the remote side what those
will cost.

Ashutosh Bapat, with very substantial cosmetic revisions by me.  Also
reviewed by Rushabh Lathia.
2015-12-22 13:46:40 -05:00
..
adminpack
auth_delay
auto_explain
btree_gin
btree_gist Fix misc typos. 2015-09-05 11:35:49 +03:00
chkpass
citext
cube Fix whitespace 2015-12-19 11:46:38 -05:00
dblink Rearrange the handling of error context reports. 2015-09-05 11:58:33 -04:00
dict_int
dict_xsyn
earthdistance Add missed CREATE EXTENSION ... CASCADE regression test adjustment. 2015-10-03 21:31:51 +02:00
file_fdw Allow foreign and custom joins to handle EvalPlanQual rechecks. 2015-12-08 12:31:03 -05:00
fuzzystrmatch
hstore Dodge a macro-name conflict with Perl. 2015-11-19 14:54:11 -05:00
hstore_plperl Dodge a macro-name conflict with Perl. 2015-11-19 14:54:11 -05:00
hstore_plpython Dodge a macro-name conflict with Perl. 2015-11-19 14:54:11 -05:00
intagg
intarray Prevent stack overflow in query-type functions. 2015-10-05 10:06:30 -04:00
isn contrib/isn now needs a .gitignore file. 2015-08-02 23:57:32 -04:00
lo
ltree Prevent stack overflow in query-type functions. 2015-10-05 10:06:30 -04:00
ltree_plpython Add CASCADE support for CREATE EXTENSION. 2015-10-03 18:23:40 +02:00
oid2name
pageinspect Add forgotten file in commit d6061f83a1 2015-11-25 16:59:07 +03:00
passwordcheck
pg_buffercache
pg_freespacemap
pg_prewarm
pg_standby Don't use function definitions looking like old-style ones. 2015-08-15 17:25:00 +02:00
pg_stat_statements Improve contrib/pg_stat_statements' handling of garbage collection failure. 2015-10-04 17:58:42 -04:00
pg_trgm
pgcrypto Avoid scan-build warning about uninitialized htonl() arguments. 2015-10-11 20:42:26 -04:00
pgrowlocks
pgstattuple
postgres_fdw postgres_fdw: Consider requesting sorted data so we can do a merge join. 2015-12-22 13:46:40 -05:00
seg
sepgsql Adjust sepgsql regression output for recent error context change 2015-09-06 11:25:36 -07:00
spi
sslinfo Fix error message wording in previous sslinfo commit 2015-09-08 11:10:20 -03:00
start-scripts
tablefunc Fix a number of places that produced XX000 errors in the regression tests. 2015-08-02 23:49:19 -04:00
tcn
test_decoding Message style improvements 2015-10-28 20:38:36 -04:00
tsearch2
tsm_system_rows Redesign tablesample method API, and do extensive code review. 2015-07-25 14:39:00 -04:00
tsm_system_time Some platforms now need contrib/tsm_system_time to be linked with libm. 2015-07-25 16:37:12 -04:00
unaccent Make unaccent handle all diacritics known to Unicode, and expand ligatures correctly 2015-09-04 12:51:53 +03:00
uuid-ossp
vacuumlo
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 "make all" and "make
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.