RE: [BUG]Update Toast data failure in logical replication
| От | tanghy.fnst@fujitsu.com |
|---|---|
| Тема | RE: [BUG]Update Toast data failure in logical replication |
| Дата | |
| Msg-id | OS0PR01MB6113F5E14AFD98EF6B3B85CCFB3F9@OS0PR01MB6113.jpnprd01.prod.outlook.com обсуждение исходный текст |
| Ответ на | Re: [BUG]Update Toast data failure in logical replication (Dilip Kumar <dilipbalaut@gmail.com>) |
| Ответы |
Re: [BUG]Update Toast data failure in logical replication
|
| Список | pgsql-hackers |
On Friday, May 28, 2021 6:51 PM, Dilip Kumar <dilipbalaut@gmail.com> wrote: > Seems you did not set the replica identity for updating the tuple. > Try this before updating, and it should work. Thanks for your reply. I tried it. > ALTER TABLE toasted_key REPLICA IDENTITY USING INDEX toasted_key_pkey; This didn't work. > or > > ALTER TABLE toasted_key REPLICA IDENTITY FULL. It worked. And I noticed if the length of PRIMARY KEY (toasted_key) is short, data could be synchronized successfully with default replicaidentity. Could you tell me why we need to set replica identity? Regards Tang
В списке pgsql-hackers по дате отправления: