From 2c63d8405bf4dcc50676f5817083fd19b1e4181a Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 4 Mar 2008 14:38:38 +0000 Subject: [PATCH] Update pg_dump item: < produce a single dump output file. > produce a single dump output file. It also would require > several sessions to share the same snapshot. --- doc/TODO | 5 +++-- doc/src/FAQ/TODO.html | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/TODO b/doc/TODO index 492e48e5f6..b9b8555ae3 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 21:48:18 EST 2008 +Last updated: Tue Mar 4 09:38:30 EST 2008 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -842,7 +842,8 @@ Clients multiple objects simultaneously The difficulty with this is getting multiple dump processes to - produce a single dump output file. + produce a single dump output file. It also would require + several sessions to share the same snapshot. http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php o Allow pg_restore to utilize multiple CPUs and I/O channels by diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index dcadc3847b..cb87f75f61 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 21:48:18 EST 2008 +Last updated: Tue Mar 4 09:38:30 EST 2008

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -750,7 +750,8 @@ first. There is also a developer's wiki at

  • Allow pg_dump to utilize multiple CPUs and I/O channels by dumping multiple objects simultaneously

    The difficulty with this is getting multiple dump processes to - produce a single dump output file. + produce a single dump output file. It also would require + several sessions to share the same snapshot. http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php

  • Allow pg_restore to utilize multiple CPUs and I/O channels by