Re: Replica Identity check of partition table on subscriber - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Replica Identity check of partition table on subscriber
Date
Msg-id CAA4eK1Jia2ZPZFMncTMuxo3npCTEdYmFfXA+p1qru2brTu4QpQ@mail.gmail.com
Whole thread Raw
In response to Re: Replica Identity check of partition table on subscriber  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Replica Identity check of partition table on subscriber
List pgsql-hackers
On Tue, Jun 21, 2022 at 7:49 AM Amit Langote <amitlangote09@gmail.com> wrote:
>
> On Mon, Jun 20, 2022 at 3:46 PM shiy.fnst@fujitsu.com
> <shiy.fnst@fujitsu.com> wrote:
> > On Mon, Jun 20, 2022 1:33 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > > One minor comment:
> > > + /*
> > > + * If it is a partitioned table, we don't check it, we will check its
> > > + * partition later.
> > > + */
> > >
> > > Can we change the above comment to: "For partitioned tables, we only
> > > need to care if the target partition is updatable (aka has PK or RI
> > > defined for it)."?
> > >
> > Thanks for your comment. Modified in the attached patches.
>
> How about: ...target "leaf" partition is updatable
>

I am not very sure if this is an improvement over the current.

> Regarding the commit message's top line, which is this:
>
>     Fix partition table's RI checking on the subscriber.
>
> I think it should spell out REPLICA IDENTITY explicitly to avoid the
> commit being confused to have to do with "Referential Integrity
> checking".
>

This makes sense. I'll take care of this.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Replica Identity check of partition table on subscriber
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Using PQexecQuery in pipeline mode produces unexpected Close messages