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.
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
<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>.
</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