Remove:

bmomjian · bmomjian · commit 60c93d3976b6 · 2008-03-04T02:48:22.000Z
&lt;
&lt; 	o To better utilize resources, restore data, primary keys, and
&lt;  	  indexes for a single table before restoring the next table
&lt;
&lt; 	  Hopefully this will allow the CPU-I/O load to be more uniform
&lt; 	  for simultaneous restores.  The idea is to start data restores
&lt; 	  for several objects, and once the first object is done, to move
&lt; 	  on to its primary keys and indexes.  Over time, simultaneous
&lt; 	  data loads and index builds will be running.
diff --git 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
@@ -8,7 +8,7 @@
 <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
 <h1><a name="section_1">PostgreSQL TODO List</a></h1>
 <p>Current maintainer:     Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
-Last updated:           Mon Mar  3 20:38:32 EST 2008
+Last updated:           Mon Mar  3 21:48:18 EST 2008
 </p>
 <p>The most recent version of this document can be viewed at<br/>
 <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -759,14 +759,6 @@ <h1><a name="section_8">Clients</a></h1>
           simultaneous operations should be performed.  Only pg_dump's
           -Fc format has the necessary dependency information.
           <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php</a>
-</p>
-    </li><li>To better utilize resources, restore data, primary keys, and
-          indexes for a single table before restoring the next table
-<p>          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.
 </p>
     </li><li>To better utilize resources, allow pg_restore to check foreign
           keys simultaneously, where possible
