diff --git a/doc/TODO b/doc/TODO index 25b8faafaef..908b7008739 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sat Jan 13 10:13:24 EST 2007 +Last updated: Tue Jan 16 22:43:34 EST 2007 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1074,9 +1074,7 @@ Vacuum o %Issue log message to suggest VACUUM FULL if a table is nearly empty? o Consider logging activity either to the logs or a system view - o Turn on by default - - http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php + o -Turn on by default Locking diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 45e1b26546d..23c4df9d01f 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Sat Jan 13 10:13:24 EST 2007 +Last updated: Tue Jan 16 22:43:34 EST 2007

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -315,7 +315,7 @@ first.

  • 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 SPI_gettypmod() to return the typemod for a TupleDesc -
  • Allow inlining of set-returning functions +
  • Implement inlining of set-returning functions defined in SQL
  • Allow SQL-language functions to return results from RETURNING queries

    • Multi-Language Support

    @@ -835,6 +835,8 @@ first.

    Currently only one hash bucket can be stored on a page. Ideally several hash buckets could be stored on a single page and greater granularity used for the hash algorithm. +

    +

    http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php

  • Consider sorting hash buckets so entries can be found using a binary search, rather than a linear scan @@ -873,6 +875,12 @@ first. 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. +

    +
  • Provide a way to calculate an "estimated COUNT(*)" +

    Perhaps by using the optimizer's cardinality estimates or random + sampling. +

    +

    http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php

  • Allow data to be pulled directly from indexes

    Currently indexes do not have enough tuple visibility information @@ -958,15 +966,16 @@ first.

  • %Issue log message to suggest VACUUM FULL if a table is nearly empty?
  • Consider logging activity either to the logs or a system view -
  • Turn on by default -

    http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php -

    +
  • -Turn on by default

    • Locking

    Startup Time Improvements