From 74fbe9ccd184c96a37c0e5b0560f486a9ff903c5 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 17 Jul 2007 00:07:54 +0000 Subject: Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions. --- doc/src/FAQ/TODO.html | 65 +++++++++++++++++++++++++++++++++------------------ 1 file changed, 42 insertions(+), 23 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 48a6222f0a1..81301c27e85 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 Jul 7 20:41:05 EDT 2007 +Last updated: Mon Jul 16 20:07:17 EDT 2007

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -38,7 +38,8 @@ first. There is also a developer's wiki at
has been reported in 8.0. A possible cause was fixed in 8.1, but it is unknown whether other problems exist. This item mostly requires additional testing rather than of writing any new code. - http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php +

+

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

  • Set proper permissions on non-system schemas during db creation

    Currently all schemas are owned by the super-user because they are copied @@ -64,7 +65,8 @@ first. There is also a developer's wiki at
    creation of rules for INSERT/UPDATE/DELETE, and constraints for rapid partition selection. Options could include range and hash partition selection. - http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php +

    +

    http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php

  • Allow auto-selection of partitioned tables for min/max() operations @@ -142,7 +144,8 @@ first. There is also a developer's wiki at
  • Allow a warm standby system to also allow read-only statements [pitr]

    This is useful for checking PITR recovery. - http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php +

    +

    http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php

  • %Create dump tool for write-ahead logs for use in determining transaction id for point-in-time recovery @@ -313,11 +316,9 @@ first. There is also a developer's wiki at

    http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php

  • Add missing parameter handling in to_char() -
    • -

    http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php +

    http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php

    -
  • UPDATE @@ -661,7 +668,8 @@ first. There is also a developer's wiki at
    is also possible to implement these capabilities in all schemas and not use a separate "packages" syntax at all. - http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php +

    +

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

  • Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
  • Allow listing of record column names, and access to @@ -688,7 +696,8 @@ first. There is also a developer's wiki at
    and allow NULL tests on such variables

    Because a row is not scalar, do not allow assignment from NULL-valued scalars. - http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php +

    +

    http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php

  • Other @@ -772,7 +781,7 @@ first. There is also a developer's wiki at
    code
  • Allow selection of individual object(s) of all types, not just tables -
  • In a selective dump, allow dumping of an object and all its +
  • In a selective dump, allow dumping of an object and all its dependencies
  • Add options like pg_restore -l and -L to pg_dump
  • Stop dumping CASCADE on DROP TYPE commands in clean mode @@ -902,6 +911,10 @@ first. There is also a developer's wiki at
    to replace the existing index file. CREATE INDEX CONCURRENTLY does not have this complication. This would allow index compaction without downtime. +

    +
  • Allow multiple indexes to be created concurrently, ideally via a + single heap scan, and have a restore of a pg_dump somehow use it +

    http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php

  • Inheritance