From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | yexiu-glory <yexiu-glory(at)qq(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 16 bug feedback |
Date: | 2025-07-17 15:54:17 |
Message-ID: | CAKFQuwbK0HjVkmxukG_R7RZAb=63+5Mh40r5c+8x+dfzUS_v+w@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thursday, July 17, 2025, yexiu-glory <yexiu-glory(at)qq(dot)com> wrote:
> I encountered a problem in PostgreSQL 16:
> In db1, there is a user table with fields id, name, phone, and createtime
> db2 replicates the user table from db1 through logical replication,
> specifying the fields as id, name, and createtime
> Then, in db1, perform the following operation: alter table user replica
> identity full;
> Then, modifying or deleting a record in the user table will result in an
> error,
> The error message for modification is as follows, and similar errors also
> occur when deleting.
> update "public"."user" set name='aaa’where id = 20005
> >ERROR: cannot update table "user"DETAIL: Column list used by the
> publication does not cover the replica identity.
>
What did you expect to happen?
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2025-07-17 16:09:08 | Re: Non-text mode for pg_dumpall |
Previous Message | Fujii Masao | 2025-07-17 15:52:31 | Re: Log prefix missing for subscriber log messages received from publisher |