TRANSACTION.

'simple' references another view that is not simple.  Must recheck
conditions after performing recursive pullup.  Per example from
Laurent Perez, 9-Jan-04.

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

Zach Irmen

select().   Add Win32 Sleep() for delay.

Claudio Natoli

ignore SIGPIPE from send() in libpq, but terminate on any other SIGPIPE,
unless the user installs their own signal handler.

This is a minor fix because the only time you get SIGPIPE from libpq's
send() is when the backend dies.

Ian Barwick

Report and fix from Martin Pitt.

datatype; the generic array comparators added in 7.4 supersede this.
Per report and patch from Korea PostgreSQL Users' Group.

Viktor Vislobokov

Give a more reasonable error message when lock file exists but has
zero length; prior code confused this with could-not-read-file case.

predicate tester.  It can now deal with commuted clauses (for
instance, 4 < x implies x > 3), subclauses more complicated than
a simple Var (for example, upper(x) = 't' implies upper(x) > 'a'),
and <> operators (for example, x < 3 implies x <> 4).  Still
only understands operators associated with btree opclasses, though.
Inspired by example from Martin Hampl.

pointer type when it is not necessary to do so.

For future reference, casting NULL to a pointer type is only necessary
when (a) invoking a function AND either (b) the function has no prototype
OR (c) the function is a varargs function.

it in the same file as the 'List' node.

> 	o Allow parameters to be specified by name and type during definition

Dennis Bjorklund's original patch for function parameter names, but
there's still plenty left to do (documentation for instance...)

> 	o -Allow parameters to be specified by name and type during definition

parameters to be declared with names.  pg_proc has a column to store
names, and CREATE FUNCTION can insert data into it, but that's all as
yet.  I need to do more work on the pg_dump and plpgsql portions of the
patch before committing those, but I thought I'd get the bulky changes
in before the tree drifts under me.
initdb forced due to pg_proc change.