Commit 2c63d840 authored by Bruce Momjian's avatar Bruce Momjian

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.
parent 27120522
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -842,7 +842,8 @@ Clients ...@@ -842,7 +842,8 @@ Clients
multiple objects simultaneously multiple objects simultaneously
The difficulty with this is getting multiple dump processes to 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 http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
o Allow pg_restore to utilize multiple CPUs and I/O channels by o Allow pg_restore to utilize multiple CPUs and I/O channels by
......
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <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>
<p>The most recent version of this document can be viewed at<br/> <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>. <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/> ...@@ -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 </li><li>Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
multiple objects simultaneously multiple objects simultaneously
<p> The difficulty with this is getting multiple dump processes to <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> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php</a>
</p> </p>
</li><li>Allow pg_restore to utilize multiple CPUs and I/O channels by </li><li>Allow pg_restore to utilize multiple CPUs and I/O channels by
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment