Re: pg_trigger.tgparentid

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: pg_trigger.tgparentid
Date: 2020-02-25 14:00:55
Message-ID: 20200225140055.GA1669@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-Feb-25, Amit Langote wrote:

> On Tue, Feb 25, 2020 at 3:58 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:

> > Thanks for pointing this out -- I agree it needed rewording. I slightly
> > adjusted your text like this:
> >
> > * Internal triggers require careful examination. Ideally, we don't
> > * clone them. However, if our parent is itself a partition, there
> > * might be internal triggers that must not be skipped; for example,
> > * triggers on our parent that are in turn clones from its parent (our
> > * grandparent) are marked internal, yet they are to be cloned.
> >
> > Is this okay for you?
>
> Thanks. Your revised text looks good, except there is a typo:
>
> in turn clones -> in turn cloned

Actually, that was on purpose ... (I also changed "were" to "are" to match.)

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Asif Rehman 2020-02-25 14:18:42 Re: WIP/PoC for parallel backup
Previous Message tushar 2020-02-25 13:56:02 Re: [Proposal] Global temporary tables