>
> 	o Add new version of PQescapeString() that doesn't double backslashes
> 	  that are part of a client-only multibyte sequence
>
> 	  Single-quote is not a valid byte in any supported client-only
> 	  encoding.
>
> 	o Add new version of PQescapeString() that doesn't double
> 	  backslashes when standard_conforming_strings is true and
> 	  non-E strings are used

> 	  o Add reporting of the current WAL file, perhaps as part of
> 	    partial log file archiving

< 	o Update pg_dump and psql to use the new COPY libpq API (Christopher)
> 	o -Update pg_dump and psql to use the new COPY libpq API (Christopher)

< 	o %Have pg_dump use multi-statement transactions for INSERT dumps

> * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have

<   multiple I/O channels simultaneously.
>   multiple I/O channels simultaneously.  One idea is to create a
>   background reader that can pre-fetch sequential and index scan
>   pages needed by other backends.  This could be expanded to allow
>   concurrent reads from multiple devices in a partitioned table.

< * Allow user-defined functions retuning a domain value to enforce domain
> * -Allow user-defined functions retuning a domain value to enforce domain

* Re-enable the GUC full_page_writes in 8.2 when reliability issues have
  been addressed

> * Allow log_min_messages to be specified on a per-module basis
>
>   This would allow administrators to see more detailed information from
>   specific sections of the backend, e.g. checkpoints, autovacuum, etc.

< * Experiment with multi-threaded backend [thread]
> * Experiment with multi-threaded backend for backend creation [thread]
1003a1004,1008
>
> * Experiment with multi-threaded backend better resource utilization
>
>   This would allow a single query to make use of multiple CPU's or
>   multiple I/O channels simultaneously.

> * Allow the creation of indexes with mixed ascending/descending
>   specifiers
>
>   This is possible now by creating an operator class with reversed sort
>   operators.  One complexity is that NULLs would then appear at the start
>   of the result set, and this might affect certain sort types, like
>   merge join.
>

> * -Eventually enable escape_string_warning and standard_conforming_strings

> 	o Prevent parent tables from altering or dropping constraints
> 	  like CHECK that are inherited by child tables
>
> 	  Dropping constraints should only be possible with CASCADE.
>

> 	o Check WSACancelBlockingCall() for interrupts (win32intr)
>

> 	o Add COPY TO STDIN / STDOUT handling

< * %Disallow changing sequence characteristics like INCREMENT for SERIAL columns
> * %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
>   does not dump the changes

> * %Disallow changing sequence characteristics like INCREMENT for SERIAL columns

> 	o Port contrib/xml2

> 	o -Add "include file" functionality in postgresql.conf

> * Allow FSM page return free space based on table clustering, to assist
>   in maintaining clustering?

> * -Allow TRUNCATE ... CASCADE/RESTRICT

< 	o %Have COPY return the number of rows loaded/unloaded?
> 	o -Have COPY return the number of rows loaded/unloaded?

> * Allow FSM to return free space toward the beginning of the heap file,
>   in hopes that empty pages at the end can be truncated by VACUUM

> * Add missing parameter handling in to_char()
>
> 	http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php
>

> * Allow to_date() and to_timestamp() accept localized month names

> * Improve port/qsort() to handle sorts with 50% unique and 50% duplicate
>   value [qsort]
>
>   This involves choosing better pivot points for the quicksort.

* Split out libpq pgpass and environment documentation sections to make
  it easier for non-developers to find

> * -Add 'tid != tid ' operator for use in corruption recovery

> 	o Allow infinite dates and intervals just like infinite timestamps

< 	o %Disallow dropping of an inherited constraint

>
> 	o Allow pg_hba.conf to specify host names along with IP addresses
>
> 	  Host name lookup could occur when the postmaster reads the
> 	  pg_hba.conf file, or when the backend starts.  Another
> 	  solution would be to reverse lookup the connection IP and
> 	  check that hostname against the host names in pg_hba.conf.
> 	  We could also then check that the host name maps to the IP
> 	  address.

> 	o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME

> * -Add COMMENT ON for all cluster global objects (roles, databases

> * -Allow to_char() to print localized month names

> * -Add system view to show free space map contents

> 	o -Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME

< 	o Improve psql's handling of multi-line statements
> 	o -Improve psql's handling of multi-line statements

> * -Allow INET + INT8 to increment the host part of the address or

< 	o Allow multi-line column values to align in the proper columns
> 	o -Allow multi-line column values to align in the proper columns

< * %Disallow changing default expression of a SERIAL column?
> * %Disallow changing default expression of a SERIAL column