Re: Conflict detection for update_deleted in logical replication
| От | Michail Nikolaev |
|---|---|
| Тема | Re: Conflict detection for update_deleted in logical replication |
| Дата | |
| Msg-id | CANtu0ohzMB38tcf2=q1HVCdz+eEpBBauHhMoATz_=YFEjDd7FQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Conflict detection for update_deleted in logical replication (Nisha Moond <nisha.moond412@gmail.com>) |
| Ответы |
RE: Conflict detection for update_deleted in logical replication
|
| Список | pgsql-hackers |
Hello, Hayato!
> Thanks for updating the patch! While reviewing yours, I found a corner case that
> a recently deleted tuple cannot be detected when index scan is chosen.
> This can happen when indices are re-built during the replication.
> Unfortunately, I don't have any solutions for it.
> a recently deleted tuple cannot be detected when index scan is chosen.
> This can happen when indices are re-built during the replication.
> Unfortunately, I don't have any solutions for it.
I just randomly saw your message, so, I could be wrong and out of the context - so, sorry in advance.
But as far as I know, to solve this problem, we need to wait for slot.xmin during the [0] (WaitForOlderSnapshots) while creating index concurrently.
Best regards,
Mikhail.
В списке pgsql-hackers по дате отправления: