Re: [HACKERS] Declarative partitioning - another take - Mailing list pgsql-hackers

From Amit Langote
Subject Re: [HACKERS] Declarative partitioning - another take
Date
Msg-id 618e767e-4316-bc03-1ae4-84203c6e506b@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] Declarative partitioning - another take  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Declarative partitioning - another take  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
On 2017/05/03 2:48, Robert Haas wrote:
> On Tue, May 2, 2017 at 3:30 AM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>> You're right.  I agree that whatever text we add here should be pointing
>> out that statement-level triggers of affected child tables are not fired,
>> when root parent is specified in the command.
>>
>> Since there was least some talk of changing that behavior for regular
>> inheritance so that statement triggers of any affected children are fired
>> [1], I thought we shouldn't say something general that applies to both
>> inheritance and partitioning.  But since nothing has happened in that
>> regard, we might as well.
>>
>> How about the attached?
> 
> Looks better, but I think we should say "statement" instead of
> "operation" for consistency with the previous paragraph, and it
> certainly shouldn't be capitalized.

Agreed, done.  Attached updated patch.

Thanks,
Amit

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] Concurrent ALTER SEQUENCE RESTART Regression
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Declarative partitioning - another take