o Allow commenting of variables in postgresql.conf to restore them
          to defaults
> 	  http://archives.postgresql.org/pgsql-patches/2007-03/msg00180.php

          o Allow a warm standby system to also allow read-only
statements
            [pitr]
> 	    http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php

* Improve speed with indexes

  For large table adjustments during VACUUM FULL, it is faster to cluster
  or reindex rather than update the index.  Also, index updates can bloat
  the index.

>
>   http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php

> 	o Have timestamp subtraction not call justify_hours()?
>
> 	  http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php
>
< 	o Add overflow checking to timestamp and interval arithmetic
> 	o Add overflow checking to timestamp and interval arithmetic

schema.relation, because the notify code only honors the relation name.
schema.relation will now generate a syntax error.

Check length of enum literals on definition and input to make sure they will fit in a name field and not cause syscache errors.

< 		o Add table function support to pltcl, plpython
> 		o Add table function support to pltcl, plpythonu
< 		o Add PL/Python tracebacks
> 		o Add PL/PythonU tracebacks
< 		o Allow PL/Python to return boolean rather than 1/0
> 		o Allow PL/PythonU to return boolean rather than 1/0

> * Fix to_date()-related functions to consistently issue errors
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
>

>
> 		o Allow PL/Python to return boolean rather than 1/0
>
> 		  http://archives.postgresql.org/pgsql-patches/2007-01/msg00596.php
>

>
> * Consider reducing memory used for shared buffer reference count
>
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php

	o Allow RETURN to return row or record functions

> 		o Allow RETURN to return row or record functions
> 		  http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php
> 		  http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php

return void ends with a SELECT, if that SELECT has a single result that is
also of type void.  Without this, it's hard to write a void function that
calls another void function.  Per gripe from Peter.

Back-patch as far as 8.0.

< * Support a data type with specific enumerated values (ENUM)
<
<   http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php
<
> * -Support a data type with specific enumerated values (ENUM)

>
> 	  http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php

some index terms.

for "vcregress check" to work.
Per report from Dave Page.

Per report from Listmail <lists@peufeu.com>

pg_type.typtype whereever practical.  Tom Dunstan, with some kibitzing
from Tom Lane.

Refactor and document the remaining mapping code.

New view pg_stat_bgwriter, and the functions required to build it.

Jun Kuwamura

add link to libpq SSL does from server docs.

Backpatch to 8.2.X.

will be released by transaction abort before _bt_end_vacuum gets called.
If either of these "can't happen" errors actually happened, we'd freeze up
trying to acquire an already-held lock.  Latest word is that this does
not explain Martin Pitt's trouble report, but it still looks like a bug.

pg_valid_server_encoding() returns the same result if the encoding is
valid.

ITAGAKI Takahiro

* Reduce storage space for small NUMERICs
>   http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php

> * Reduce storage space for small NUMERICs
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php
>

< 	o Add more logical syntax CLUSTER table USING index;
> 	o Add more logical syntax CLUSTER table USING index;

        o Add more logical syntax CLUSTER table USING index;
< 	o Add more logical syntax CLUSTER table ORDER BY index;
> 	o Add more logical syntax CLUSTER table USING index;

required memory context when handling client-specified parameter types
for an unnamed statement.  Per report from Kris Jurka.

 ecpglib supports it.
Change configure (patch from Bruce) and msvc build system to no longer require
 pthreads on win32, since all parts of postgresql can be thread-safe using the
 native platform functions.

  win32 threads.
- Fixed regression tests to run threading tests.

--- Simon.
Also, code review and cleanup for the previous COPY-no-WAL patches --- Tom.

properties of the "text" type, and then simplify the code accordingly.
Patch from Jeremy Drake.

from PuTTY with is under minimal BSD/MIT license. Marko Kreen.

its table list and then rechecks pgstat before vacuuming each table to
verify that no one has vacuumed the table in the meantime.

In the current autovacuum world this only means that a worker will not
vacuum a table that a user has vacuumed manually after the worker started.
When support for multiple autovacuum workers is introduced, this will reduce
the probability of simultaneous workers on the same database doing redundant
work.

ITAGAKI Takahiro