From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Jim Nasby <jim(at)nasby(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_restore --no-post-data and --post-data-only |
Date: | 2011-08-26 16:46:11 |
Message-ID: | CA+TgmoaW3-WfgBzXsFrPpFFWcAqisSXsa=y3hRGaTN16Ya5kAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 26, 2011 at 11:22 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> But we could also add these switches to pg_dump too if people feel it's
>> worthwhile. I haven't looked but the logic should not be terribly hard.
>
> Something like the attached, in fact, which seems pretty simple.
It seems like there are three sets of things you might want here:
pre-data, data, post-data. So in the end we could end up with:
--pre-data-only
--post-data-only
--data-only
--no-pre-data
--no-post-data
--no-data
And then maybe someone will want just the create index commands and
not the constraint commands. It seems like it might be more elegant
to come up with a single switch where you can list which things you
want:
--sections='predata data'
--sections='postdata'
--sections='index'
Just thinking out loud....
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2011-08-26 17:08:52 | Re: pg_restore --no-post-data and --post-data-only |
Previous Message | hubert depesz lubaczewski | 2011-08-26 15:28:35 | Re: [GENERAL] pg_upgrade problem |