Fixed bug with '=' operator for gist__int_ops and
     define '=' operator for gist__intbig_ops opclass.
     Now '=' operator is consistent with standard 'array' type.

     Thanks Achilleus Mantzios for bug report and suggestion.

Oleg Bartunov

of link() under Cygwin:

    http://archives.postgresql.org/pgsql-cygwin/2002-04/msg00072.php

Note that it appears that BeOS and Netware also have the above or
similar problem.

I have only verified that PostgreSQL builds under Cygwin with this
patch.
Since I cannot reproduce the problem, I cannot verify that the proposed
patch solves it.  Nevertheless, both Barry Pederson and David P.
Caldwell
attest that this patch solves the problem.  See the following for
details:

    http://archives.postgresql.org/pgsql-cygwin/2002-05/msg00043.php
    http://archives.postgresql.org/pgsql-cygwin/2002-05/msg00040.php

Jason Tishler

fixed bug reported by cc.ais40@wanadoo.fr where getObject was returning an Integer for a smallint datatype instead of a Short

> * Allow DEFERRABLE UNIQUE constraints

Permaine Cheung

> 	o -Abort all SET changes made in an aborted transaction

> * -Add deleted bit to index tuples to reduce heap access

fixed bug reported by Noel Rappin (nrappin@sockeye.com) java Array type handled Timestamps incorrectly

with the Cursor object's fetchmany() method.  The API and
inline documentation state that the default is 1.  It
currently defaults to 5.

Patrick Macdonald

CONSTRAINTS.

Neil Conway <neilconway@rogers.com>

> * Add FILLFACTOR to btree index creation

 precision storage format. Previously applied the same math as used for the
 64-bit integer storage format case, which was wrong.
 Problem introduced recently when the 64-bit storage format was
 implemented.

a multicolumn-capable index AM *must* support nulls in index columns
after the first one.

that would do the wrong thing with BLOB OIDs exceeding 2G.

> * Add BSD-licensed qsort() for Solaris