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()

"syslog" option.)

By the way: The "virtual_host" parameter is a bad name for that
particular option, I think. "Virtual host" signals that PostgreSQL will
behave differently according to which IP address it's contacted (like
Apache's virtual host support which makes the web-server serve different
sites according to different criteria). A better word for the options
would be "tcpip_listen_addr" or something like that.

Troels Arvin

configure to report if they are not found.

and test them, in addition to testing the underlying LargeObject API methods.

 Modified Files:
 	jdbc/build.xml jdbc/org/postgresql/test/jdbc2/BlobTest.java

using the V3 protocol.

 Modified Files:
 	jdbc1/AbstractJdbc1Connection.java

faster, but more importantly does not leak memory.  Still needs more work
though, per my recent note to pgsql-hackers.

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

the #includes it depends on.

We don't actually need the flag, so just #define it as zero in such cases.

Christopher Kings-Lynne

Update to POSIX getpwuid_r() function.

Larry Rosenman

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.

just before CommitTransactionCommand().  This is a more sensible place
to put it since commit discards a lot of contexts, and we'd not find
out about stomps affecting only transaction-local contexts.

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

in hopes of soothing fears of those with partial IPv6 support.  Still an
open question whether we should report EAFNOSUPPORT errors at all,
though.

PQexecParams is used with a statement that doesn't return data.

processing loop; avoids extra overhead when using parse/bind/execute
messages instead of single Query message.