:-(, and tidies it up a little as well.

Regards, Dave.

*before* acquiring shlock on buffer context. This way we should be
protected against conflicts with FlushRelationBuffers.
(Seems we never do excl lock and then StartBufferIO for the same
buffer, so there should be no deadlock here, - but we'd better
check this very soon).

well, here goes our first Release Candidate for 7.1 *cross fingers*

Tom Lane.

(inadequate anyway) mention of SELECT INTO from the main SELECT ref page.
Point out that SELECT INTO means something else in plpgsql and ecpg.

source data, improve split algorithm for intbig_ops.  Oleg Bartunov
with some kibitzing from Tom Lane.

on HPUX.

it's easier to tell whether a bug report is talking about progressive
memory exhaustion or a wacko requested chunk size.

per gripe from Josh Berkus.

 - Avoid forcing table name to lower case in FixupBlobXrefs
 - Removed fmtId calls for all ArchiveEntry name fields. This fixes
   quoting problems in trigger enable/disable code for mixed case
   table names, and avoids commands like 'pg_restore -t '"TblA"'

sloppiness (insufficient parenthesization, etc).
It still fails regress test for me, however.

see if it's been updated.  Skip the whole mess if we didn't see any
old pidfile.

NEXTXID isn't really necessary, per previous discussion in pghackers,
but I mulishy insisted we should put it in anyway.  Mea culpa.

space in front of it.  Improve comments a little.

I'm betting the QNX4 port does not either ...

work in BeOS port.

which caused segfault in a data-only retore with BLOBs

slow backend, if we update unconditionally as the code did before).

the new log file with zeroes, only while renaming it into place.  This should
prevent problems with 'stuck spinlock' errors under heavy load.