Re: pg_dump additional options for performance

bruce wrote:
> Joshua D. Drake wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On Mon, 3 Mar 2008 20:33:08 -0500 (EST)
> > Bruce Momjian <bruce@momjian.us> wrote:
> > 
> > > Added to TODO based on this discussion:
> > > 
> > >         o Allow pg_dump to utilize multiple CPUs and I/O channels by
> > > dumping multiple objects simultaneously
> > > 
> > >           The difficulty with this is getting multiple dump processes
> > > to produce a single dump output file.
> > >           http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
> > 
> > Isn't part of this problem also a consistent snapshot?
> 
> Yes, that might also be an issue though I thought we had some ideas
> about snapshot sharing.

OK, I have added the possible requirement of shared snapshots to that
pg_dump TODO item.  Thanks.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +