Re: pgsql: Add --section option to pg_dump and pg_restore. - Mailing list pgsql-committers

From Thom Brown
Subject Re: pgsql: Add --section option to pg_dump and pg_restore.
Date
Msg-id CAA-aLv58H5_DamJtr4xh7ng9357PagThun=FaPVuW1Xd3Jd6=A@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Add --section option to pg_dump and pg_restore.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-committers
On 17 December 2011 18:11, Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> On 12/17/2011 08:13 AM, Thom Brown wrote:
>>
>> On 17 December 2011 02:32, Andrew Dunstan<andrew@dunslane.net>  wrote:
>>>
>>>
>>> On 12/16/2011 07:57 PM, Thom Brown wrote:
>>>>
>>>> On 17 December 2011 00:17, Andrew Dunstan<andrew@dunslane.net>    wrote:
>>>>>
>>>>> Add --section option to pg_dump and pg_restore.
>>>>>
>>>>> Valid values are --pre-data, data and post-data. The option can be
>>>>> given more than once. --schema-only is equivalent to
>>>>> --section=pre-data --section=post-data. --data-only is equivalent
>>>>> to --section=data.
>>>>
>>>> "Post-data items consist of definitions of indexes, triggers, rules
>>>> and constraints other than check constraints."
>>>>
>>>> What about NOT VALID check constraints?  Those are required to be
>>>> post-data.
>>>>
>>>
>>> Hmm, yeah. Are they the only ones?
>>
>> Well, there's object permissions too excluding ownership, but can't
>> think of anything else.
>>
>
> I have qualified the sentence above to say that the exception is "validated
> check constraints".

Sounds good to me.

> The comments in the code about when ACLs are dumped or restored appear to be
> incorrect unless I'm missing something. The appear to be dumped where they
> occur. (This code always makes my head hurt, I confess.)

Dumped where they occur?  I'm not sure I follow.

--
Thom

pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: pgsql: Same clarification for pg_restore.
Next
From: Tom Lane
Date:
Subject: pgsql: Add SP-GiST (space-partitioned GiST) index access method.