mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update pg_dump item:

Browse Source 
< 	  produce a single dump output file.
> 	  produce a single dump output file.  It also would require
> 	  several sessions to share the same snapshot.
This commit is contained in:
Bruce Momjian 2008-03-04 14:38:38 +00:00
parent 271205223a
commit 2c63d8405b
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/TODO
View File

@ -1,7 +1,7 @@
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
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

5
doc/src/FAQ/TODO.html
View File

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