| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_restore --no-post-data and --post-data-only |
| Date: | 2011-11-13 01:56:18 |
| Message-ID: | 4EBF23C2.2010105@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
cheers
andrew
| Attachment | Content-Type | Size |
|---|---|---|
| pg_dump_sections.patch | text/x-patch | 6.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-11-13 07:47:06 | Re: why do we need two snapshots per query? |
| Previous Message | Robert Haas | 2011-11-13 01:47:10 | Re: why do we need two snapshots per query? |