Re: WIP patch for parallel pg_dump - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP patch for parallel pg_dump
Date
Msg-id AANLkTikqXMPUk9Mnn+BvWyiouajGTQJPAOM--G0Zanbc@mail.gmail.com
Whole thread Raw
In response to Re: WIP patch for parallel pg_dump  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: WIP patch for parallel pg_dump  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Fri, Dec 3, 2010 at 8:02 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
> I think Josh Berkus' comments in the thread you mentioned are correct:
>
>> Actually, I'd say that there's a broad set of cases of people who want
>> to do a parallel pg_dump while their system is active.  Parallel pg_dump
>> on a stopped system will help some people (for migration, particularly)
>> but parallel pg_dump with snapshot cloning will help a lot more people.

But you failed to quote the rest of what he said:

> So: if parallel dump in single-user mode is what you can get done, then
> do it.  We can always improve it later, and we have to start somewhere.
> But we will eventually need parallel pg_dump on active systems, and
> that should remain on the TODO list.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: should we set hint bits without dirtying the page?
Next
From: Alvaro Herrera
Date:
Subject: Re: improving foreign key locks