Re: Replica Identity check of partition table on subscriber
| От | Amit Langote |
|---|---|
| Тема | Re: Replica Identity check of partition table on subscriber |
| Дата | |
| Msg-id | CA+HiwqHz_+a=fw0vw7DtDHEW+=BZYdxkTFYxCse==S1LaA4bAQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | RE: Replica Identity check of partition table on subscriber ("shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>) |
| Ответы |
Re: Replica Identity check of partition table on subscriber
|
| Список | pgsql-hackers |
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
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".
--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: