From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Jim Nasby" <jim(at)nasby(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com> |
Subject: | Re: pg_restore --no-post-data and --post-data-only |
Date: | 2011-11-15 23:14:53 |
Message-ID: | 54825.184.180.152.2.1321398893.squirrel@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, November 12, 2011 8:56 pm, Andrew Dunstan wrote:
>
>
> On 08/26/2011 05:11 PM, Tom Lane wrote:
>> Alvaro Herrera<alvherre(at)commandprompt(dot)com> writes:
>>> The "--section=data --section=indexes" proposal seems very reasonable
>>> to
>>> me -- more so than "--sections='data indexes'".
>> +1 ... not only easier to code and less squishily defined, but more like
>> the existing precedent for other pg_dump switches, such as --table.
>>
>>
>
>
> Here is a patch for that for pg_dump. The sections provided for are
> pre-data, data and post-data, as discussed elsewhere. I still feel that
> anything finer grained should be handled via pg_restore's --use-list
> functionality. I'll provide a patch to do the same switch for pg_restore
> shortly.
>
> Adding to the commitfest.
>
Updated version with pg_restore included is attached.
cheers
andrew
Attachment | Content-Type | Size |
---|---|---|
dump_sections.patch | text/x-patch | 14.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2011-11-15 23:44:09 | Re: ISN was: Core Extensions relocation |
Previous Message | Robert Haas | 2011-11-15 22:54:52 | Re: FlexLocks |