|
8 | 8 | <bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
|
9 | 9 | <h1><aname="section_1">PostgreSQL TODO List</a></h1>
|
10 | 10 | <p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
11 |
| -Last updated:Mon Mar3 21:48:18 EST 2008 |
| 11 | +Last updated:Tue Mar4 09:38:30 EST 2008 |
12 | 12 | </p>
|
13 | 13 | <p>The most recent version of this document can be viewed at<br/>
|
14 | 14 | <ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
|
@@ -750,7 +750,8 @@ <h1><a name="section_8">Clients</a></h1>
|
750 | 750 | </li><li>Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
|
751 | 751 | multiple objects simultaneously
|
752 | 752 | <p> The difficulty with this is getting multiple dump processes to
|
753 |
| - produce a single dump output file. |
| 753 | + produce a single dump output file. It also would require |
| 754 | + several sessions to share the same snapshot. |
754 | 755 | <ahref="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php</a>
|
755 | 756 | </p>
|
756 | 757 | </li><li>Allow pg_restore to utilize multiple CPUs and I/O channels by
|
|