From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Parallel pg_dump for 9.1 |
Date: | 2010-03-29 20:43:33 |
Message-ID: | 4BB110F5.6070001@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
>
> It's completely possible that you could want to clone a server for dev
> and have more CPU and I/O bandwidth available than can be efficiently
> used by a non-parallel pg_dump. But certainly what Joachim is talking
> about will be a good start. I think there is merit to the
> synchronized snapshot stuff for pg_dump and perhaps other applications
> as well, but I think Joachim's (well-taken) point is that we don't
> have to treat it as a hard prerequisite.
>
>
>
Possibly. I think the most useful thing that could be done right now is
probably the least controversial, namely creating a directory type of
archive, with support for pg_restore, including parallel pg_restore.
Personally I think that's worth doing in its own right anyway.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-03-29 21:05:48 | Re: Alpha release this week? |
Previous Message | Stefan Kaltenbrunner | 2010-03-29 20:40:11 | Re: Alpha release this week? |