Re: Logical replication claims to work, not working - new tables - Mailing list pgsql-general

From Chris Angelico
Subject Re: Logical replication claims to work, not working - new tables
Date
Msg-id CAPTjJmrQuB20ARvTrpqUv7EUyz=WWC3hEgFANzkDf74gUZF3Gg@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication claims to work, not working - new tables  (Chris Angelico <rosuav@gmail.com>)
List pgsql-general
On Mon, 22 Jan 2024 at 05:50, Chris Angelico <rosuav@gmail.com> wrote:
>
> On Mon, 22 Jan 2024 at 05:25, Justin <zzzzz.graf@gmail.com> wrote:
> > Adding a primary key will fix this issue.  Note PG 16 can use indexes to find qualifying rows when a table's
replicais set to full.
 
>
> I'll try dropping the table, creating it again with a PK, and seeing
> how it goes. Thanks.
>

Okay, it seems to be working now. Thanks! Hopefully that was the only issue.

I'm a bit surprised by this, the docs do seem to imply that it ought
to work (albeit inefficiently). Maybe I made it worse by initially
creating the table without specifying the replica identity, and had to
alter it in afterwards?

ChrisA



pgsql-general by date:

Previous
From: Chris Angelico
Date:
Subject: Re: Logical replication claims to work, not working - new tables
Next
From: James Pang
Date:
Subject: how to trace a backend session