unneeded configure work.

slight resemblance to their actual behavior.

this variable on the command line.

	http://developer.postgresql.org/~momjian/upgrade_tips_7.3

ACT and ACST were already present.  AMT and AMST conflict with the
existing entries for Armenia; no change there for the moment.

> * Add a libpq function to support Parse/DescribeStatement capability

	* Allow TRUNCATE ... CASCADE/RESTRICT

> * -Add btree index support for reltime, tinterval, regproc (Tom)

are now driven by the default btree opclass, rather than assuming that
particular operator names have the needed semantics.

> * Allow PREPARE of cursors

This useless routine will removed in 7.5. It's already discussed (see
hackers list archive).

Karel Zak

> * Fix upper()/lower() to work for multibyte encodings
>

spelling mistake in the PREPARE ref page (2) Makes some
English more consistent, in the ref pages for some of the
client apps (3) Adds a link to the libpq docs in the
vacuumdb ref page.

Neil Conway

have cursors that might outlive their creating transactions. A
patch is attached that fixes this (suggestions on better wording
are welcome).

Neil Conway

> * Allow pooled connections to query prepared queries
> * Allow pooled connections to close all open WITH HOLD cursors

any use of CIDR masks - here's a patch that adds  a couple of  sample
lines and associated comments.

Andrew Dunstan

binary format read/created by COPY BINARY. It also mentions the
contrib/binarycopy module.

Lee Kindness.

> * Add ALTER DOMAIN, AGGREGATE, CONVERSION, SEQUENCE ... OWNER TO
>

> * Add TRUNCATE ... CASCADE

> * Add pg_get_acldef(), pg_get_typedefault(), and pg_get_attrdef()

initial response is 'S', not 'Y', when it is willing to do SSL.

via extended query protocol, because it sends Sync right after Execute
without realizing that the command to be executed is COPY.  There seems
to be no reasonable way for it to realize that, either, so the best fix
seems to be to make the backend ignore Sync during copy-in mode.  Bit of
a wart on the protocol, but little alternative.  Also, libpq must send
another Sync after terminating the COPY, if the command was issued via
Execute.

libpq users to perform Bind/Execute of previously prepared statements.
Per yesterday's discussion, this offers enough performance improvement
to justify bending the 'no new features during beta' rule.

tree. This also catches lots of little Makefile bugs, so here's a small
patch for one of them (replacing an explicit reference to thread.c with
a reference to it as the first prerequsite of the rule makes make look
for it in the place where it was found (the source tree) rather than in
the build tree. (using GNU make 3.79.1)

John Gray

> * Prevent unneeded quoting in psql \d output using fmtId()