From 2c63d8405bf4dcc50676f5817083fd19b1e4181a Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
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 492e48e5f62..b9b8555ae3d 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 dcadc3847ba..cb87f75f615 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 21:48:18 EST 2008
+Last updated: Tue Mar 4 09:38:30 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>.
@@ -750,7 +750,8 @@ first. There is also a developer's wiki at<br/>
</li><li>Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
multiple objects simultaneously
<p> 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.
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php</a>
</p>
</li><li>Allow pg_restore to utilize multiple CPUs and I/O channels by
--
GitLab