right circumstances it would leave old and new bucket headers pointing to
the same list of records.

(no sense to hold it) or we'll be out of lock entries.
Great thanks to Hiroshi Inoue.

(Curious that gcc doesn't complain about this code...).

is poor coding style.  I agree.

file headers, to conform to established Postgres coding style and avoid
warnings from gcc.

after checking for presence of C++ compiler.  Odd we hadn't seen any
reports of problems before...

when used with egcs --- now it does.

2. Get rid of locking when updating statistics in vacuum.
3. Use QuerySnapshot in COPY TO and call SetQuerySnashot
   in main tcop loop before FETCH and COPY TO.

few percent speedup in INSERT...

redundant) SearchSysCache searches per table column in an INSERT, which
accounted for a good percentage of the CPU time for INSERT ... VALUES().
Now it only does two searches in the typical case.

cache access routines.

through MAXBACKENDS array entries used to be fine when MAXBACKENDS = 64.
It's not so cool with MAXBACKENDS = 1024 (or more!), especially not in a
frequently-used routine like SIDelExpiredDataEntries.  Repair by making
procState array size be the soft MaxBackends limit rather than the hard
limit, and by converting SIGetProcStateLimit() to a macro.

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.