On Mon, May 17, 2021 at 6:47 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Mon, May 17, 2021 at 12:30 PM Peter Smith <smithpb2...@gmail.com> wrote: > > [...] > > The essence of the trouble seems to be that the apply_handle_truncate > > function never anticipated it may end up truncating the same table > > from 2 separate workers (subscriptions) like this test case is doing. > > Probably this is quite an old problem because the > > apply_handle_truncate code has not changed much for a long time. > > > > Yeah, have you checked it in the back branches? >
Yes, the apply_handle_truncate function was introduced in April/2018 [1]. REL_11_0 was tagged in Oct/2018. The "ERROR: deadlock detected" log is reproducible in PG 11.0. ---------- [1] https://github.com/postgres/postgres/commit/039eb6e92f20499ac36cc74f8a5cef7430b706f6 Kind Regards, Peter Smith. Fujitsu Australia.
