do the right thing: look for a NOTICE message from the backend before we
close our side of the socket.  6.4 libpq did not reliably print the backend's
hara-kiri message, 'The Postmaster has informed me ...', because it only
did the right thing if connection closure was detected during a read
attempt instead of a write attempt.

new -x option to skip acl dump.

Update for v6.5 release.

but the Makefile does break non g++.

 <<mak.patch>>
Andreas

before any tuples are loaded, preserve the default '1000 tuples' table
size estimate.

the backend does.  Remove unnecessary limitation on field size in
dumpClasses_dumpData (ie, -d or -D case).

Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
 *except* for the porting list which will require a report
 from a successful installation to be updated.

Some wording changes from Vadim's original text doc.
Processes cleanly, but may need fixup.

Normalize markup for vacuumdb; content is the same.

postgres-ref.sgml is not yet marked up.

inserts.  Change some variables to bool to be clearer.

Give BEOS a chance ...

BT_READ/BT_WRITE are BUFFER_LOCK_SHARE/BUFFER_LOCK_EXCLUSIVE now.
Also get rid of #define BT_VERSION_1 - we use version 1 as default
for near two years now.

LockBuffer is used to acquire read/write access
to index pages. Pages are released before leaving
index internals.

not be marked inFromCl any longer. Otherwise the planner gets confused
and joins over them where in fact it does not have to.

Adjust hasSubLinks now with a recursive lookup - could be wrong in
multi action rules because parse state isn't reset correctly and all
actions in the rule are marked hasSubLinks if one of them has.

Jan

Jan

GROUP BY or ORDER BY expressions in INSERT ... SELECT.

aggregate functions, as in
	select a, b from foo group by a;
The ungrouped reference to b is not kosher, but formerly we neglected to
check this unless there was an aggregate function somewhere in the query.