Jason Tishler's credit, if it's broken it's my fault ...

datatype.  Perhaps someday we can figure out a way of getting reproducible
results from testing this type, but for now ...

Thanks to Tom.

starting with '$'.

the current state of and the issues with PostgreSQL on Windows.

Thanks,
Jason

--
Jason Tishler

- Dump CHECK constraints in OID order

VFD entries.  On platforms where dereferencing a null pointer doesn't
lead to coredump, it's possible that this omission could have led to
unpleasant behavior like deleting the wrong file.

include O_CREAT.

physical file has disappeared.  There is no really good reason why
relcache should be opening the underlying file at all, AFAICS.
In any case we needn't raise a hard error here.

with different default values, unless the child table redeclares the
column with an explicit default.  This was judged to be the approach
least likely to cause unpleasant surprises.

 NetBSD/arm, NetBSD/VAX, OpenBSD/Sparc, Solaris, Ultrix.

now on VAX NetBSD.  Hence, remove #ifdef'd disable tests.

case of LIMIT in a sub-select.

RC2 preparations ...

the UDT/function order problem.

    - Rudimentary support for dependencies in archives.
      Uses dependencies to modify the OID used in sorting TOC
      entries. This will NOT handle multi-level dependencies,
      but will manage simple relationships like UDTs & their functions.

    - Treat OIDs with more respect (avoid using ints, use macros
      for conversion & comparison).

Jason Tishler.

ready.  It appears that most (all?) Unixen will consider a socket to
be read or write ready if it has an error condition, but of course
Microsoft does things differently.

in CREATE TABLE, but give a warning notice.  Clean up inconsistent
handling of defaults and NOT NULL flags from multiply-inherited columns.
Per pghackers discussion 28-Mar through 30-Mar.