supresses compiler warning.

>   http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php

Joachim Wieland

the DROP pass rather than the ADD_CONSTR pass.  On examining the code I
think this was just an oversight rather than intentional, and it seems
to satisfy the principle of least surprise better than the alternative
solution that was discussed.  Add an example to the ref page showing how
to do ALTER TYPE and update the default in one command.  Per gripe from
Markus Bertheau that that wasn't possible.

check).  This isn't supported by pg_regress since the recent rewrite
into C.  While we could add char classes to pg_regress.c's code, it's
not really needed at the moment: thanks to Andrew's patch to make
pg_regress always accept the 'standard' comparison file, we can just
drop the version check.

rather than pointers to garbage, when calling AFTER STATEMENT triggers.
Michael Fuhr

'mod' and 'all', which is not the right order.  SGML documentation order
was correct. Report from Chander Ganesan.

in recent -t/-n/-T/-N patch.

Small style cleanups.

temporary context that can be reset when advancing to the next sublist.
This is faster and more thorough at recovering space than the previous
method; moreover it will do the right thing if something in the sublist
tries to register an expression context callback.

as grantees, not PUBLIC ... and you can't say GROUP either.  Noted by
Brian Hurt.

transformInsertStmt: the target table is already in p_rtable at that point.

test to avoid expensive contain_vars_of_level() scan in the normal case
where we're not inside a rule.

Implemented EXEC SQL UNDEF.
Applied first version of the regression test patch by Joachim Wieland <joe@mcknight.de>.

< 	o Add COPY TO STDIN / STDOUT handling
> 	o Add COPY TO STDIN handling

> 	o In rules, allow VALUES() to contain a mixture of 'old' and 'new'
> 	  references

        o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)

(e.g. "INSERT ... VALUES (...), (...), ...") and elsewhere as allowed
by the spec. (e.g. similar to a FROM clause subselect). initdb required.
Joe Conway and Tom Lane.

of the text where appropiate.

lightweight locks.

Marc Munro

if table creation failed (the table already exists).

Martin Pitt

< 	o %Allow pg_dump to use multiple -t and -n switches  [pg_dump]
<
< 	  http://archives.postgresql.org/pgsql-patches/2006-01/msg00190.php
<
> 	o -Allow pg_dump to use multiple -t and -n switches, exclusion
> 	   ability, and regular expression object matching

and -N options to exclude objects.  Also support regular expressions for
option object names.

Greg Sabino Mullane

have pg_regress fall back on testing with the canonical results file if an
alternative test is specified but none succeeds.

Joshua D. Drake
Robert Treat

> * Consider compressed annealing to search for query plans
>
>   This might replace GEQO, http://sixdemonbag.org/Djinni.

(table or index) before trying to open its relcache entry.  This fixes
race conditions in which someone else commits a change to the relation's
catalog entries while we are in process of doing relcache load.  Problems
of that ilk have been reported sporadically for years, but it was not
really practical to fix until recently --- for instance, the recent
addition of WAL-log support for in-place updates helped.

Along the way, remove pg_am.amconcurrent: all AMs are now expected to support
concurrent update.