From: | "Jochem van Dieten" <jochemd(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump additional options for performance |
Date: | 2008-02-24 13:22:32 |
Message-ID: | f96a9b830802240522u2dbf4cdci51b2bfc58ecabd25@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 11, 2008 at 5:51 PM, Tom Lane wrote:
> I agree. Since any multiple-output-file case can't usefully use stdout,
> I think we should combine the switches and just have one switch that
> says both that you want separated output and what the target filename
> is. Thus something like
>
> --pre-schema-file = foo
> --data-file = bar
> --post-schema-file = baz
Or we could have a switch that specifies a directory and have pg_dump
split the dump not just in pre-schema, data and post-schema, but also
split the data in a file for each table. That would greatly facilitate
a parallel restore of the data through multiple connections.
Jochem
From | Date | Subject | |
---|---|---|---|
Next Message | andy | 2008-02-24 14:21:18 | Re: 8.3 / 8.2.6 restore comparison |
Previous Message | Gregory Stark | 2008-02-24 11:23:56 | Re: RFP: Recursive query in 8.4 |