only the inner-side relation would be considered as potential equijoin clauses,
which is wrong because the condition doesn't necessarily hold above the point
of the outer join.  Per test case from Kevin Grittner (bug#1916).

subsystem reliability.

Victor Vislobokov

< * +Add options to pg_config to show the share_dir, sysconfdir,
<   pkgincludedir, and localedir

building contrib with USE_PGXS.  To make it work all the way, the
pg_regress script would need to be included in the installation tree.

relocated after installation.  We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config.  This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.

to avoid useless multiple executions of pg_config.

to be less error-prone.

> 	o Improve signal handling,
> 	  http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php

< * Add options to pg_config to show the share_dir, sysconfdir,
> * +Add options to pg_config to show the share_dir, sysconfdir,

out-of-memory --- that is, return NULL rather than dumping core.
Noted by Qingqing Zhou.

Marko Kreen

< * Allow protocol-level EXECUTE that is actually a fetch to appear
<   in the logs as a fetch rather than another execute

adjusted from a patch by Simon.

> * Allow protocol-level BIND parameter values to be logged
> * Allow protocol-level EXECUTE that is actually a fetch to appear
>   in the logs as a fetch rather than another execute

outer relation is empty did not work, per test case from Patrick Welche.
It tried to use nodeHashjoin.c's high-level mechanisms for fetching an
outer-relation tuple, but that code expected the hash table to be filled
already.  As patched, the code failed in corner cases such as having no
outer-relation tuples for the first hash batch.  Revert and rewrite.

DLL compiles to not match the application.

compatibility issue.

for int8 and related types.  However we might be talking to a client
that has working int64; so pq_getmsgint64 really needs to check the
incoming value and throw an overflow error if we can't represent it
accurately.

> * Simplify dropping roles that have objects in several databases

> 	o Allow PL/PgSQL to support WITH HOLD cursors