RE: [BUG] Unexpected action when publishing partition tables - Mailing list pgsql-hackers

From houzj.fnst@fujitsu.com
Subject RE: [BUG] Unexpected action when publishing partition tables
Date
Msg-id OS0PR01MB5716A07CE2B3B2F30A626D0594DC9@OS0PR01MB5716.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: [BUG] Unexpected action when publishing partition tables  (vignesh C <vignesh21@gmail.com>)
Responses Re: [BUG] Unexpected action when publishing partition tables  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tuesday, September 14, 2021 10:41 PM vignesh C <vignesh21@gmail.com> wrote:
> On Tue, Sep 7, 2021 at 11:38 AM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote:
> >
> >
> > Attach new version patches which addressed the comment.
> 
> Thanks for fixing this issue. The bug gets fixed by the patch, I did not find any
> issues in my testing.
> I just had one minor comment:
> 
> We could clean the table at the end by calling DROP TABLE testpub_parted2:
> +-- still fail, because parent's publication replicates updates UPDATE
> +testpub_parted2 SET a = 2;
> +ERROR:  cannot update table "testpub_parted2" because it does not
> have a replica identity and publishes updates
> +HINT:  To enable updating the table, set REPLICA IDENTITY using ALTER
> TABLE.
> +ALTER PUBLICATION testpub_forparted DROP TABLE testpub_parted;
> +-- works again, because update is no longer replicated UPDATE
> +testpub_parted2 SET a = 2;

Thanks for the comment.
Attach new version patches which clean the table at the end.

Best regards,
Hou zj

Attachment

pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Logical replication keepalive flood
Next
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Column Filtering in Logical Replication