Re: "ERROR: deadlock detected" when replicating TRUNCATE

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: "ERROR: deadlock detected" when replicating TRUNCATE
Дата
Msg-id CAA4eK1JviDzy3EdCHdtFjCNqevksNk5JrMB32xqs9qcjM_vpOw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: "ERROR: deadlock detected" when replicating TRUNCATE  (Dilip Kumar <dilipbalaut@gmail.com>)
Ответы Re: "ERROR: deadlock detected" when replicating TRUNCATE  (Dilip Kumar <dilipbalaut@gmail.com>)
Re: "ERROR: deadlock detected" when replicating TRUNCATE  (Peter Smith <smithpb2250@gmail.com>)
Список pgsql-hackers
On Mon, May 17, 2021 at 3:05 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Mon, May 17, 2021 at 12:30 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> > PSA a patch adding a test for this scenario.
>
> I am not sure this test case is exactly targeting the problematic
> behavior because that will depends upon the order of execution of the
> apply workers right?
>

Yeah, so we can't guarantee that this test will always reproduce the
problem but OTOH, I have tried two times and it reproduced both times.
I guess we don't have a similar test where Truncate will replicate to
two subscriptions, otherwise, we would have caught such a problem.
Having said that, I am fine with leaving this test if others feel so
on the grounds that it won't always lead to the problem reported.

-- 
With Regards,
Amit Kapila.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bharath Rupireddy
Дата:
Сообщение: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?
Следующее
От: Dilip Kumar
Дата:
Сообщение: Re: "ERROR: deadlock detected" when replicating TRUNCATE