| From: | Chris Angelico <rosuav(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication claims to work, not working - new tables |
| Date: | 2024-01-21 19:28:09 |
| Message-ID: | CAPTjJmrQuB20ARvTrpqUv7EUyz=WWC3hEgFANzkDf74gUZF3Gg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 22 Jan 2024 at 05:50, Chris Angelico <rosuav(at)gmail(dot)com> wrote:
>
> On Mon, 22 Jan 2024 at 05:25, Justin <zzzzz(dot)graf(at)gmail(dot)com> wrote:
> > Adding a primary key will fix this issue. Note PG 16 can use indexes to find qualifying rows when a table's replica is 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Pang | 2024-01-22 07:29:27 | how to trace a backend session |
| Previous Message | Chris Angelico | 2024-01-21 18:50:57 | Re: Logical replication claims to work, not working - new tables |