From d32f24776fb6780aaf3c08019692778b7bff1b82 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 7 Dec 2007 17:52:15 +0000 Subject: Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output --- doc/src/FAQ/TODO.html | 126 +++++++++++--------------------------------------- 1 file changed, 27 insertions(+), 99 deletions(-) (limited to 'doc/src/FAQ') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 215176f1926..8b141ac26df 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Mon Nov 26 18:31:05 EST 2007
+Last updated: Fri Dec 7 12:52:05 EST 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -95,9 +95,7 @@ first. There is also a developer's wiki at
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
@@ -133,8 +131,6 @@ first. There is also a developer's wiki at
requires a tool that will call that function and connect to each
database to find the objects in each database for that tablespace.
http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php - http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php - http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php -
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php
http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php -
-http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php - http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php
http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php
@@ -195,7 +176,6 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php
http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php
http://developer.postgresql.org/index.php/XML_Support
@@ -280,7 +260,6 @@ first. There is also a developer's wiki athttp://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php
-http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
- http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
@@ -369,7 +343,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php
This might require some background daemon to maintain clustering
during periods of low usage. It might also require tables to be only
partially filled for easier reorganization. Another idea would
@@ -601,8 +573,6 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php
- http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
@@ -740,7 +707,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
-http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php
http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
-http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php
- This is difficult because it requires datatype-specific knowledge.
@@ -980,7 +932,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
@@ -1056,7 +1004,7 @@ first. There is also a developer's wiki athttp://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php
-http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
@@ -1127,7 +1068,7 @@ first. There is also a developer's wiki athttp://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
-http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php
@@ -1210,7 +1149,6 @@ first. There is also a developer's wiki at Allow tables to bypass WAL writes and just fsync() dirty pages on
@@ -1229,12 +1167,10 @@ first. There is also a developer's wiki at
of indexes on TOAST tables.
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php
-http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php -
-http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php - http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php
http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php
@@ -1379,7 +1308,6 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php
-