From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_restore --no-post-data and --post-data-only |
Date: | 2011-09-03 21:04:42 |
Message-ID: | 4E62966A.6030103@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/03/2011 04:49 PM, Dimitri Fontaine wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>>> Oh, I meant just having it create separate custom format files for each
>>> database. As shell scripts all over the world have been doing for years,
>>> but it would be nice if it was simply built in.
>> I guess it could be done, although I'm not going to do it :-) I'm more about
>> making somewhat hard things easier than easy things slightly easier :-)
> Then what about issuing an archive (tar or ar format here) containing
> one custom file per database plus the globals file, SQL, plus maybe a
> database listing, and hacking pg_restore so that it knows what to do
> with such an input ?
>
> Bonus points if that supports the current -l and -L options, of course.
>
>
That's probably a lot of code for a little benefit, at least from my
POV, but others might find it useful.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-09-03 23:18:47 | Large C files |
Previous Message | Dimitri Fontaine | 2011-09-03 21:03:16 | Re: WAL "low watermark" during base backup |