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

> * Allow GRANT/REVOKE permissions to be inherited by objects based on
>   schema permissions

<   BY col {DESC} LIMIT 1. Completing this item involves making this
>   BY col {DESC} LIMIT 1. Completing this item involves doing this
<   invalidated if anyone modifies the table.
<
>   invalidated if anyone modifies the table.  Another idea is to
>   get a count directly from a unique index, but for this to be
>   faster than a sequential scan it must avoid access to the heap
>   to obtain tuple visibility information.
>
> * Allow data to be pulled directly from indexes
>
>   Currently indexes do not have enough tuple tuple visibility
>   information to allow data to be pulled from the index without
>   also accessing the heap.  One way to allow this is to set a bit
>   to index tuples to indicate if a tuple is currently visible to
>   all transactions when the first valid heap lookup happens.  This
>   bit would have to be cleared when a heap tuple is expired.
>

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

< * Allow building with directories containing spaces
> * Allow building in directories containing spaces
<   There are two capabilities here, first the ability to build from a
<   source directory that contains spaces, and second the ability to install
<   into a directory that contains spaces.  The first is probably not
<   possible because 'gmake' and other compiler tools do not fully support
<   spaces in path names.  The second is possible with proper quoting in
<   the makefiles.  Because PostgreSQL supports relocatable installs, it
<   is possible to install into a directory that doesn't contain spaces and
<   then copy the install to a directory with spaces.
>   This is probably not possible because 'gmake' and other compiler tools
>   do not fully support quoting of paths with spaces.
>
> * Allow installing to directories containing spaces
>
>   This is possible if proper quoting is added to the makefiles for the
>   install targets.  Because PostgreSQL supports relocatable installs, it
>   is already possible to install into a directory that doesn't contain
>   spaces and then copy the install to a directory with spaces.

>   There are two capabilities here, first the ability to build from a
>   source directory that contains spaces, and second the ability to install
>   into a directory that contains spaces.  The first is probably not
>   possible because 'gmake' and other compiler tools do not fully support
>   spaces in path names.  The second is possible with proper quoting in
>   the makefiles.  Because PostgreSQL supports relocatable installs, it
>   is possible to install into a directory that doesn't contain spaces and
>   then copy the install to a directory with spaces.

> * Allow building with directories containing spaces

< 	  the Win32 wcscoll() can be used.
> 	  the Win32 wcscoll() can be used, and perhaps other functions
> 	  like towupper().

< 	  the Win32 strcoll() can be used.
> 	  the Win32 wcscoll() can be used.

<         o Disallow encodings like UTF8 which which PostgreSQL supports
>         o Disallow encodings like UTF8 which PostgreSQL supports
914a915,917
>
> 	  To fix UTF8, the data needs to be converted to UTF16 and then
> 	  the Win32 strcoll() can be used.

> * Improve the background writer
>
>   Allow the background writer to more efficiently write dirty buffers
>   from the end of the LRU cache and use a clock sweep algorithm to
>   write other dirty buffers to reduced checkpoint I/O

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

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

> * Allow psql \pset boolean variables to set to fixed values, rather than toggle

>         o Disallow encodings like UTF8 which which PostgreSQL supports
>           but the operating system does not (already disallowed by
> 	  pginstaller)

< 	o Allow the shared memory address to be configured via GUC

< 	o Remove per-backend parameter file and move into shared memory

Add for Win32:
> 	o Allow the shared memory address to be configured via GUC

>
> * Allow the size of the buffer cache used by temporary objects to be
>   specified as a GUC variable
>
>   Larger local buffer cache sizes requires more efficient handling of
>   local cache lookups.

> * ANALYZE should record a pg_statistic entry for an all-NULL column

> * Fix priority ordering of read and write light-weight locks (Neil)

<
> 	o Fix problem with shared memory on the Win32 Terminal Server

> 	o Improve dlerror() reporting string

> * Allow a warm standby system to also allow read-only queries
>
>   This is useful for checking PITR recovery.
>

> * Fix psql's display of schema information (Neil)

>
> * Allow FOR UPDATE queries to do NOWAIT locks
>

> * Allow ecpg to work with MSVC and BCC

< 	  returns in data?
> 	  returns in data

< * Make log_min_duration_statement output when the duration is reached rather
<   than when the statement completes
<
<   This prints long queries while they are running, making trouble shooting
<   easier.  Also, it eliminates the need for log_statement because it
<   would now be the same as a log_min_duration_statement of zero.

> * Make log_min_duration_statement output when the duration is reached rather
>   than when the statement completes
>
>   This prints long queries while they are running, making trouble shooting
>   easier.  Also, it eliminates the need for log_statement because it
>   would now be the same as a log_min_duration_statement of zero.

< you would like to work on an item, please read the developer's FAQ
> you would like to work on an item, please read the Developer's FAQ

9c5
< Last updated:		Mon Nov 29 23:33:09 EST 2004
> Last updated:		Tue Nov 30 00:03:37 EST 2004
13a10,16
> #A hyphen, "-", marks changes that will appear in the upcoming 8.1 release.#
>
> Bracketed items, "[]", have more detail.
>
> This list contains all known PostgreSQL bugs and feature requests. If
> you would like to work on an item, please read the developer's FAQ
> first.

> * Prevent INET cast to CIDR from droping netmask, SELECT '1.1.1.1'::inet::cidr

> 	o Allow COPY FROM ... CVS to interpret newlines and carriage
> 	  returns in data?
>
> 	  This would require major refactoring of the copy source code.