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)

        - is not initialized to 1 (at least in the WIN_32 code I started with!)

Claudio Natoli

Other cleanups as discussed.

This is his original version with a binary rmdir() we might need in the
future.

I will commit an update version with cleanups shortly.

Remove the 'strategy map' code, which was a large amount of mechanism
that no longer had any use except reverse-mapping from procedure OID to
strategy number.  Passing the strategy number to the index AM in the
first place is simpler and faster.
This is a preliminary step in planned support for cross-datatype index
operations.  I'm committing it now since the ScanKeyEntryInitialize()
API change touches quite a lot of files, and I want to commit those
changes before the tree drifts under me.

> * Have psql '\i ~/<tab><tab>' actually load files it displays from home dir

instructions were way out of date and incorrect.  Installing Postgres
from Cygwin is easier these days than the FAQ would imply.

This patch already includes Andrew's previous patch.

Christopher Kings-Lynne

> * Have psql \dn show only visible schemas using current_schemas()

> * Use more reliable method for CREATE DATABASE to get a consistent copy of db
>

RENAME TO option.

patch by Kris Jurka

they do not prevent the postmaster from deleting the shmem segment during
a post-backend-crash restart cycle.  Per recent discussion.

else it cannot be used to handle failures detected during WAL replay.
Fortunately this flag isn't actually enforced yet, but get it right.

> * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
>   by searching for non-conflicting constraint names, and prefix with table name