diff options
| author | Bruce Momjian <bruce@momjian.us> | 2008-03-04 02:48:22 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2008-03-04 02:48:22 +0000 |
| commit | 60c93d3976b626625462b6de68d0e30d8bd94ce8 (patch) | |
| tree | 0fbbb4b44d0eea7dc5fa9ba13e80b4e72783e619 /doc/src | |
| parent | 66504d763f9a95331aea9006fc8a19eb22e39edc (diff) | |
Remove:
<
< 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.
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/FAQ/TODO.html | 10 |
1 files changed, 1 insertions, 9 deletions
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 792d69bff3b..dcadc3847ba 100644 --- 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>. @@ -760,14 +760,6 @@ first. There is also a developer's wiki at<br/> -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 </li><li>Allow pg_restore to create all indexes of a table |