Re: [HACKERS] transition table behavior with inheritance appearsbroken (was: Declarative partitioning - another take) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] transition table behavior with inheritance appearsbroken (was: Declarative partitioning - another take)
Date
Msg-id CAEepm=2BZf-KD3WuUaA1kHvvDM0quaWgMjNcjBdGKXZDc6arSw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] transition table behavior with inheritance appearsbroken (was: Declarative partitioning - another take)  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] transition table behavior with inheritance appearsbroken (was: Declarative partitioning - another take)  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
On Fri, May 19, 2017 at 6:35 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> On 2017/05/19 15:16, Thomas Munro wrote:
>> Would TransitionCaptureState be a better name for this struct?
>
> Yes.  Although, losing the Trigger prefix might make it sound a bit
> ambiguous though.  Right above its definition, we have TriggerData.  So,
> maybe TriggerTransitionCaptureState or TriggerTransitionCaptureData or
> TriggerTransitionData may be worth considering.

Ok, here's a version using TransitionCaptureState.  Those other names
seem too long, and "TriggerTransition" is already in use so
"TriggerTransitionData" seems off the table.  Having the word
"capture" in there seems good, since this is an object that controls
what we capture when we process a modify a set of tables.  I hope
that's clear.

-- 
Thomas Munro
http://www.enterprisedb.com

-- 
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: Petr Jelinek
Date:
Subject: Re: [HACKERS] Multiple table synchronizations are processed serially
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] TAP tests - installcheck vs check