<
> 	o Add -f to pg_dumpall

> 	o -Allow NULLs in arrays

>
> * Add estimated_count(*) to return an estimate of COUNT(*)
>
>   This would use the planner ANALYZE statistatics to return an estimated
>   count.

<   so duplicate checking can be easily performed.
>   so duplicate checking can be easily performed.  It is possible to
>   do it without a unique index if we require the user to LOCK the table
>   before the MERGE.

< * Add a libpq function to support Parse/DescribeStatement capability
< * Add PQescapeIdentifier() to libpq
< * Prevent PQfnumber() from lowercasing unquoted the column name
<
<   PQfnumber() should never have been doing lowercasing, but historically
<   it has so we need a way to prevent it
<
648a642,661
>
>
> libpq
>
> 	o Add a function to support Parse/DescribeStatement capability
> 	o Add PQescapeIdentifier()
> 	o Prevent PQfnumber() from lowercasing unquoted the column name
>
> 	  PQfnumber() should never have been doing lowercasing, but
> 	  historically it has so we need a way to prevent it
>
> 	o Allow query results to be automatically batched to the client
>
> 	  Currently, all query results are transfered to the libpq
> 	  client before libpq makes the results available to the
> 	  application.  This feature would allow the application to make
> 	  use of the first result rows while the rest are transfered, or
> 	  held on the server waiting for them to be requested by libpq.
> 	  One complexity is that a query like SELECT 1/col could error
> 	  out mid-way through the result set.

>
>   To implement this cleanly requires that the table have a unique index
>   so duplicate checking can be easily performed.
>

< 	o Allow ALTER TABLE RENAME CONSTRAINT
> 	o Add ALTER TABLE RENAME CONSTRAINT, update index name also

> 	o Have ALTER INDEX update the name of a constraint using that index
> 	o Allow ALTER TABLE RENAME CONSTRAINT

< 	o Add a GUC variable to allow output of interval values in ISO8601
< 	  format
212a211,223
> 	o Add a GUC variable to allow output of interval values in ISO8601
> 	  format
> 	o Improve timestamptz subtraction to be DST-aware
>
> 	  Currently, subtracting one date from another that crosses a
> 	  daylight savings time adjustment can return '1 day 1 hour', but
> 	  adding that back to the first date returns a time one hour in
> 	  the future.  This is caused by the adjustment of '25 hours' to
> 	  '1 day 1 hour', and '1 day' is the same time the next day, even
> 	  if daylight savings adjustments are involved.
>
> 	o Fix interval display to support values exceeding 2^31 hours
> 	o Add overflow checking to timestamp and interval arithmetic

>
> 	o Add auto-expanded mode so expanded output is used if the row
> 	  length is wider than the screen width.
>
> 	  Consider using auto-expanded mode for backslash commands like \df+.

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

> * Prevent PQfnumber() from lowercasing unquoted the column name
>
>   PQfnumber() should never have been doing lowercasing, but historically
>   it has so we need a way to prevent it
>

< * Prevent libpq's PQfnumber() from lowercasing the column name
<
<   One idea is to lowercase all identifiers except those that are
<   surrounded by quotes.
<

<
< * Add code to detect an SMP machine and handle spinlocks accordingly
<   from distributted.net, http://www1.distributed.net/source,
<   in client/common/cpucheck.cpp
<
<   On SMP machines, it is possible that locks might be released shortly,
<   while on non-SMP machines, the backend should sleep so the process
<   holding the lock can complete and release it.

< 	o %Add dumping of comments on composite type columns
< 	o %Add dumping of comments on index columns
< 	o Stop dumping CASCADE on DROP TYPE commands in clean mode
> 	o %Add dumping of comments on index columns and composite type columns
604a603
> 	o Stop dumping CASCADE on DROP TYPE commands in clean mode

< 	o %Replace crude DELETE FROM method of pg_dumpall --clean for
<           cleaning of roles with separate DROP commands
608a607
>

<
> 	o Allow pg_dump --clean to drop roles that own objects or have
> 	  privileges

< * Prevent libpq's PQfnumber() from lowercasing the column name?
> * Prevent libpq's PQfnumber() from lowercasing the column name
>
>   One idea is to lowercase all identifiers except those that are
>   surrounded by quotes.
>

> 	o Add options like pg_restore -l and -L to pg_dump

> 	o Allow selection of individual object(s) of all types, not just
> 	  tables
> 	o In a selective dump, allow dumping of an object and all its
> 	  dependencies

< * Consider compressing indexes by storing key prefix values shared by
> * Consider compressing indexes by storing key values duplicated in
735a736,737
>
>   This is difficult because it requires datatype-specific knowledge.

<
> * Consider compressing indexes by storing key prefix values shared by
>   several rows as a single index entry

< * -Have sequence dependency track use of DEFAULT sequences

< * Have sequence dependency track use of DEFAULT sequences,
<   seqname.nextval?
> * -Have sequence dependency track use of DEFAULT sequences

< * +Add options to pg_config to show the share_dir, sysconfdir,
<   pkgincludedir, and localedir

> 	o Improve signal handling,
> 	  http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php

< * Add options to pg_config to show the share_dir, sysconfdir,
> * +Add options to pg_config to show the share_dir, sysconfdir,

< * Allow protocol-level EXECUTE that is actually a fetch to appear
<   in the logs as a fetch rather than another execute

> * Allow protocol-level BIND parameter values to be logged
> * Allow protocol-level EXECUTE that is actually a fetch to appear
>   in the logs as a fetch rather than another execute

> * Simplify dropping roles that have objects in several databases

> 	o Allow PL/PgSQL to support WITH HOLD cursors

>
> 	o Display IN, INOUT, and OUT parameters in \df+
>
> 	  It probably requires psql to output newlines in the proper
> 	  column, which is already on the TODO list.

> * Add function to report the time of the most recent server reload

> * Add options to pg_config to show the share_dir, sysconfdir,
>   pkgincludedir, and localedir
>

> * Allow CREATE INDEX to take an additional parameter for use with
>   special index types
>

>
> 	  Another idea would be to allow actual SELECT queries in a COPY.

>
> 	o Allow COPY to output from views
>

<   This would be beneficial when there are few distinct values.
>   This would be beneficial when there are few distinct values.  This is
>   already used by GROUP BY.
946d946
< * Allow DISTINCT to use hashing like GROUP BY

< * Allow WAL traffic to be steamed to another server for stand-by
> * Allow WAL traffic to be streamed to another server for stand-by

> * Allow DISTINCT to use hashing like GROUP BY