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

>
> * Interpret INTERVAL '1:30' MINUTE TO SECOND as '1 minute 30 seconds'

> * Add support for ANSI time INTERVAL syntax, INTERVAL '1 2:03:04' DAY TO SECOND
> * Add support for ANSI date INTERVAL syntax, INTERVAL '1-2' YEAR TO MONTH
> * Process mixed ANSI/PG INTERVAL syntax, and round value to requested precision
184a188,189
>   Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS INTERVAL
>   MONTH), and this should return '12 months'

< * Allow a warm standby system to also allow read-only queries

> * Allow WAL replay of CREATE TABLESPACE to work when the directory
>   structure on the recovery computer is different from the original

> 	o Update pg_dump and psql to use the new COPY libpq API

< 	o Update to use the newer COPY syntax

> 	o Update to use the newer COPY syntax

>
> * Support table partitioning that allows a single table to be stored
>   in subtables that are partitioned based on the primary key or a WHERE
>   clause

<
< 	o Prevent conflicting SET options from being set
<
< 	  This requires a checking function to be called after the server
< 	  configuration file is read.

> * -Allow the size of the buffer cache used by temporary objects to be

<   SQL-spec compliant, so allow such handling to be disabled.
>   SQL-spec compliant, so allow such handling to be disabled.  However,
>   disabling backslashes could break many third-party applications and tools.

> * Allow sequential scans to take advantage of other concurrent
>   sequentiqal scans, also called "Synchronised Scanning"

<         o Disallow encodings like UTF8 which PostgreSQL supports
<           but the operating system does not (already disallowed by
< 	  pginstaller)
>         o Add support for Unicode
< 	  To fix UTF8, the data needs to be converted to UTF16 and then
< 	  the Win32 wcscoll() can be used, and perhaps other functions
> 	  To fix this, the data needs to be converted to/from UTF16/UTF8
>           so the Win32 wcscoll() can be used, and perhaps other functions
< 	  locales but provides no ordering.
<
> 	  locales but provides no ordering or character set classes.

> * -Cache last known per-tuple offsets to speed long tuple access

> * Support triggers on columns (Greg Sabino Mullane)

< 	o Allow COPY FROM ... CSV to interpret newlines and carriage
> 	o -Allow COPY FROM ... CSV to interpret newlines and carriage

* -Add a warning when the free space map is too small

> * Fix cross-compiling of time zone database via 'zic'

	UNICODE => UTF8
	ALT => WIN866
	WIN => WIN1251
	TCVN => WIN1258

The old codes continue to work.

> * -Make src/port/snprintf.c thread-safe

> * Improve psql's handling of multi-line queries

< 	  like towupper().
> 	  like towupper().  However, UTF8 already works with normal
> 	  locales but provides no ordering.

> 	o -Change PL/PgSQL to use palloc() instead of malloc()

> 	* Add internationalized message strings

< * Add the client IP address to pg_stat_activity
> * Add the client IP address and port to pg_stat_activity

< * Allow server configuration parameters to be remotely modified
> * Allow pg_hba.conf settings to be controlled via SQL
>
>   This would require a new global table that is dumped to flat file for
>   use by the postmaster.  We do a similar thing for pg_shadow currently.
>

< * Consider use of open/fcntl(O_DIRECT) to minimize OS caching
> * Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
>   especially for WAL writes

<   The agreed syntax is:
>   The proposed syntax is:

>   The agreed syntax is:
> 	GRANT SELECT ON ALL TABLES IN public TO phpuser;
> 	GRANT SELECT ON NEW TABLES IN public TO phpuser;
>

< 	o Allow COPY FROM ... CVS to interpret newlines and carriage
> 	o Allow COPY FROM ... CSV to interpret newlines and carriage

> * Add xpath_array() to /contrib/xml2 to return results as an array

> * Allow the creation of indexes with mixed ascending/descending specifiers

> * Make src/port/snprintf.c thread-safe

< * Add IP address to pg_stat_activity
> * Add the client IP address to pg_stat_activity

> * Add IP address to pg_stat_activity

< *  Allow the PITR process to be debugged and data examined
> * Allow the PITR process to be debugged and data examined

the item:

< 	o Automatic failover
<
< 	  The proper solution to this will probably the use of a master/slave
< 	  replication solution like Sloney and a connection pooling tool like
< 	  pgpool.
<

<   all temporary tables, removal of any NOTIFYs, etc.  This could be used
<   for connection pooling.  We could also change RESET ALL to have this
<   functionality.
>   all temporary tables, removal of any NOTIFYs, cursors, prepared
>   queries(?), currval()s, etc.  This could be used for connection pooling.
>   We could also change RESET ALL to have this functionality.

< * Change LIMIT/OFFSET to use int8
> * Change LIMIT/OFFSET and FETCH/MOVE to use int8