< * -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

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

< * Research use of sched_yield() for spinlock acquisition failure

>
1032a1034
> * Remove BeOS and QNX-specific code

> 	o Fix SELECT INTERVAL '1' MONTH

<
> * Update Bonjour to work with newer cross-platform SDK

<
390d388
<
453c451
< 	  removed or have its heap and index files truncated.  One
> 	  be removed or have its heap and index files truncated.  One
< * Use a phantom command counter for nested subtransactions to reduce
<   per-tuple overhead

> 	o Add single-step debugging of PL/PgSQL functions

<   cmin/cmax pair and is stored in local memory.
>   cmin/cmax pair and is stored in local memory.  Another idea is to
>   store both cmin and cmax only in local memory.

< 	  have its heap and index files truncated.  One issue is
< 	  that no other backend should be able to add to the table
< 	  at the same time, which is something that is currently
< 	  allowed.
> 	  removed or have its heap and index files truncated.  One
> 	  issue is that no other backend should be able to add to
> 	  the table at the same time, which is something that is
> 	  currently allowed.

> 	o Allow COPY on a newly-created table to skip WAL logging
450a452,456
> 	  On crash recovery, the table involved in the COPY would
> 	  have its heap and index files truncated.  One issue is
> 	  that no other backend should be able to add to the table
> 	  at the same time, which is something that is currently
> 	  allowed.

< 	o Allow COPY into an empty table to skip WAL logging
> 	o Allow COPY into an new table to skip WAL logging

> * Use UTF8 encoding for NLS messages so all server encodings can
>   read them properly
<         o %Add support for Unicode
<
< 	  To fix this, the data needs to be converted to/from UTF16/UTF8
<           so the Win32 wcscoll() can be used, and perhaps other functions
< 	  like towupper().  However, UTF8 already works with normal
< 	  locales but provides no ordering or character set classes.

<   could only see committed rows from another transaction. However,
>   could only see rows from another completed transaction. However,
981c981
<   proper visibility of the row, for example, for cursors.
>   proper visibility of the row's cmin, for example, for cursors.

> 	o Allow COPY into an empty table to skip WAL logging

* Merge xmin/xmax/cmin/cmax back into three header fields

  Before subtransactions, there used to be only three fields needed to
  store these four values. This was possible because only the current
  transaction looks at the cmin/cmax values. If the current transaction
  created and expired the row the fields stored where xmin (same as
  xmax), cmin, cmax, and if the transaction was expiring a row from a
  another transaction, the fields stored were xmin (cmin was not
  needed), xmax, and cmax. Such a system worked because a transaction
  could only see committed rows from another transaction. However,
  subtransactions can see rows from outer transactions, and once the
  subtransaction completes, the outer transaction continues, requiring
  the storage of all four fields. With subtransactions, an outer
  transaction can create a row, a subtransaction expire it, and when the
  subtransaction completes, the outer transaction still has to have
  proper visibility of the row, for example, for cursors.

  One possible solution is to create a phantom cid which represents a
  cmin/cmax pair and is stored in local memory.

< * Maintain a map of recently-expired rows
<
<   This allows vacuum to target specific pages for possible free space
<   without requiring a sequential scan.
<
Update entry:

>   One complexity is that index entries still have to be vacuumed, and
>   doing this without an index scan (by using the heap values to find the
>   index entry) might be slow and unreliable, especially for user-defined
>   index functions.

> * Eventually enable escape_string_warning and standard_conforming_strings

> * Add function to return the thread safety status of libpq and ecpg

> * Allow user-defined types to specify a type modifier at table creation
>   time

>
>   Another issue is whether underlying table changes should be reflected
>   in the view, e.g. should SELECT * show additional columns if they
>   are added after the view is created.

> 	o Issue a warning if a change-on-restart-only postgresql.conf value
> 	  is modified  and the server config files are reloaded
> 	o Mark change-on-restart-only values in postgresql.conf
205a209
> 	o Fix SELECT '0.01 years'::interval, '0.01 months'::interval