diff --git a/doc/TODO b/doc/TODO index e21fb6bb27..492e48e5f6 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,7 +1,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Mon Mar 3 20:38:32 EST 2008 +Last updated: Mon Mar 3 21:48:18 EST 2008 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -853,15 +853,6 @@ Clients -Fc format has the necessary dependency information. http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php - o To better utilize resources, restore data, primary keys, and - indexes for a single table before restoring the next table - - Hopefully this will allow the CPU-I/O load to be more uniform - for simultaneous restores. The idea is to start data restores - for several objects, and once the first object is done, to move - on to its primary keys and indexes. Over time, simultaneous - data loads and index builds will be running. - o To better utilize resources, allow pg_restore to check foreign keys simultaneously, where possible o Allow pg_restore to create all indexes of a table diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 792d69bff3..dcadc3847b 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: Mon Mar 3 20:38:32 EST 2008 +Last updated: Mon Mar 3 21:48:18 EST 2008

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -759,14 +759,6 @@ first. There is also a developer's wiki at
simultaneous operations should be performed. Only pg_dump's -Fc format has the necessary dependency information. http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php -

-
  • To better utilize resources, restore data, primary keys, and - indexes for a single table before restoring the next table -

    Hopefully this will allow the CPU-I/O load to be more uniform - for simultaneous restores. The idea is to start data restores - for several objects, and once the first object is done, to move - on to its primary keys and indexes. Over time, simultaneous - data loads and index builds will be running.

  • To better utilize resources, allow pg_restore to check foreign keys simultaneously, where possible