Re: PostgreSQL 16 bug feedback
От | yexiu-glory |
---|---|
Тема | Re: PostgreSQL 16 bug feedback |
Дата | |
Msg-id | tencent_9C7D93BE7D2985B131FA723E64C2C051650A@qq.com обсуждение исходный текст |
Ответ на | PostgreSQL 16 bug feedback ("yexiu-glory" <yexiu-glory@qq.com>) |
Список | pgsql-hackers |
发件人:David G. Johnston <david.g.johnston@gmail.com> 发件时间:2025年7月18日 01:56 收件人:yexiu-glory <yexiu-glory@qq.com> 主题:Re: PostgreSQL 16 bug feedback |
I hope there will be no errors and it can be updated and deleted normally.---原始邮件---发件人:"David G. Johnston"发送时间:2025-07-17 23:54:17收件人:"yexiu-glory";主题:Re: PostgreSQL 16 bug feedbackOn Thursday, July 17, 2025, yexiu-glory <yexiu-glory@qq.com> wrote:I encountered a problem in PostgreSQL 16:In db1, there is a user table with fields id, name, phone, and createtimedb2 replicates the user table from db1 through logical replication, specifying the fields as id, name, and createtimeThen, 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.
I think it would be better if, when using the command "alter table user replica identity full" and specifying columns, the full-state synchronization should also synchronize all the specified fields?
В списке pgsql-hackers по дате отправления: