| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_dump additional options for performance |
| Date: | 2008-03-04 13:53:34 |
| Message-ID: | 200803041353.m24DrYM12083@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, 3 Mar 2008 20:33:08 -0500 (EST)
> Bruce Momjian <bruce(at)momjian(dot)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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin M. Roy | 2008-03-04 14:02:27 | 8.3.0 Core with concurrent vacuum fulls |
| Previous Message | Bruce Momjian | 2008-03-04 13:51:41 | Re: [PATCHES] Show INHERIT in \du |