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

>
> 	o Display IN, INOUT, and OUT parameters in \df+
>
> 	  It probably requires psql to output newlines in the proper
> 	  column, which is already on the TODO list.

> * Add function to report the time of the most recent server reload

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

integrated autovacuum now does :)

David Fetter

maintenance.sgml.

Robert Treat

[ Also fix create domain markup.]

David Fetter

> * Allow CREATE INDEX to take an additional parameter for use with
>   special index types
>

release notes.

"optimization".  When we find a potentially useful joinclause, we
have to add all its other required_relids to the result, not only the
other clause_relids.  They are different in the case of a joinclause
whose applicability has to be postponed due to outer join.  We have
to include the extra rels because otherwise, after best_inner_indexscan
masks the join rels with index_outer_relids, it will always fail to
find the joinclause as applicable.  Per report from Husam Tomeh.