From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: "ERROR: deadlock detected" when replicating TRUNCATE |
Date: | 2021-05-18 01:22:05 |
Message-ID: | CAHut+PuY2H4OsTHsafF0wf43JTJyTRj5nh1XqQy+vrDMpDC7dw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 17, 2021 at 6:47 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Mon, May 17, 2021 at 12:30 PM Peter Smith <smithpb2250(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-05-18 01:24:36 | Re: Move pg_attribute.attcompression to earlier in struct for reduced size? |
Previous Message | Chapman Flack | 2021-05-18 01:19:00 | Re: allow specifying direct role membership in pg_hba.conf |