advancing ActiveSnapshot when we are inside a volatile function.
Per example from Gaetano Mendola.  Add a regression test to catch
similar problems in future.

after an unknown or failed psql backslash command, and also while
discarding "extra" arguments of a putatively valid backslash command.
In the case of an unknown/failed command, make sure we discard the
whole rest of the line, rather than trying to resume at the next
backslash.  Per discussion with Thomer Gil.

> * Allow psql \pset boolean variables to set to fixed values, rather than toggle

DLL pginstaller installs.

R?mi Zara

Robert Treat

Ian Barwick

Per example from Florian Pflug.

rather than in $(top_builddir)/src/backend/postgres.  Sean Chittenden

several reports of users being confused when they attempt to use ELSEIF
and run into trouble due to PL/PgSQL's lax parser. The parser will be
improved for 8.1, but we can fix most of the problem by allowing ELSEIF
for now.

Adjust documentation to match current reality.

usefully be larger than 255.  Per gripe from Simon Riggs.

>         o Disallow encodings like UTF8 which which PostgreSQL supports
>           but the operating system does not (already disallowed by
> 	  pginstaller)

gripe from John Gray.  Also fix thinko in pltcl Makefile: if a special
Tcl include directory is specified, that ought to be searched first.

PTHREAD_LIBS to all libpq-usage builds.

binary compiles, and adjust configure tests for AIX.

from goranpop@nspoint.net.  I think this escaped notice because in
simple cases the list is NIL on entry.

silently ignored, allowing one to write bizarre things like
	DECLARE x setof int;
in plpgsql.  This has misled at least one novice into thinking that
plpgsql variables could be sets ...

redundant cross-datatype comparisons.  Per example from Merlin Moncure.

checks, to ensure the previous test backend has time to quit out of the
regression database.  Also, allow all the checks to be run even if one
of them fails.  Per suggestions from Andrew Dunstan to improve the
usefulness of buildfarm testing.

thought there couldn't be any, but the folly of this was exposed by an
example from andrew@supernews.com 5-Dec-2004.  The patch applies the
identical logic already used for table constraints and defaults to ON
SELECT rules, so I have reasonable confidence in it even though it might
look like complicated logic.

be emitted too soon.  The previous code got this right in the case where
the CHECK was emitted as a separate ALTER TABLE command, but not in the
case where the CHECK is emitted right in CREATE TABLE.  Per report from
Slawomir Sudnik.

Note: this code is pretty ugly; it'd perhaps be better to treat comments
as independently sortable dump objects.  That'd be much too invasive a
change for RC time though.