to try additional addresses returned from getaddrinfo() if the first one
fails at the bind() or connect() steps.  Per yesterday's discussion.

a comma between multiple column_constraint's for a single column.
Per report from Tomislaw Kitynski.

can terminate the bootstrap run.

double or out-of-sequence output with child process.

data directory.  Also fix handling of error conditions associated with
data directory checking step (can't use a boolean to distinguish four
possible result states...)

usage of PGSemaMagic, the minimum required value is actually 537, but
say 1000 just to use a round number.  255 is *not* good enough.

and the cache replacement strategy as well as a description of the
ARC algorithm and the special tailoring of that done for PostgreSQL.

Jan

of option switches for backend, fix handling of COPY from data files so
that we won't have the newline-after-\. issue back again, add back some
comments and printouts lost from the shell script, etc.  Still needs work
for error handling; in particular the shell version worked much more
nicely for the case of a postgres executable that fails on invocation.

add a header comment/copyright notice.

Andrew Dunstan

I added a couple more Assertions while tracking down the exact
cause of the former bug.

All 93 regression tests pass now.

Jan

Jan

Christopher Kings-Lynne

come out before the action is done.

algorithm adopted for PostgreSQL.

Jan

my fault.  Adding it fixes bogus message display when reading a block
comment at the end of a script file.

pghackers proposal of 8-Nov.  All the existing cross-type comparison
operators (int2/int4/int8 and float4/float8) have appropriate support.
The original proposal of storing the right-hand-side datatype as part of
the primary key for pg_amop and pg_amproc got modified a bit in the event;
it is easier to store zero as the 'default' case and only store a nonzero
when the operator is actually cross-type.  Along the way, remove the
long-since-defunct bigbox_ops operator class.

website for install as service, because it's a quite a long and complex
process.

Christopher Kings-Lynne

> * Ignore temporary tables from other session when processing inheritance

RESTRICT is not deferrable to the create table reference
page.

Stephan Szabo

> * Add free-behind capability for large sequential scans (fadvise)