Re: postgres crash on concurrent update of inheritance partitionedtable
От
Oleksii Kliukin
Тема
Re: postgres crash on concurrent update of inheritance partitionedtable
Дата
Msg-id
EDC3F2AC-53D1-407C-82AC-954A700FF059@hintbits.com
Ответ на
Список
Дерево обсуждения
postgres crash on concurrent update of inheritance partitioned table Oleksii Kliukin <alexk@hintbits.com>
Re: postgres crash on concurrent update of inheritance partitionedtable Tomas Vondra <tomas.vondra@2ndquadrant.com>
Re: postgres crash on concurrent update of inheritance partitioned table Tom Lane <tgl@sss.pgh.pa.us>
Re: postgres crash on concurrent update of inheritance partitioned table Tom Lane <tgl@sss.pgh.pa.us>
Re: postgres crash on concurrent update of inheritance partitionedtable Andres Freund <andres@anarazel.de>
Re: postgres crash on concurrent update of inheritance partitionedtable Oleksii Kliukin <alexk@hintbits.com>
Tom Lane wrote: > Tomas Vondra writes: >> On Tue, Jan 28, 2020 at 05:17:14PM +0100, Oleksii Kliukin wrote: >>> We have experienced a few crashes a day since upgrading to pg 12.1 last >>> week, during the process of updating an inheritance-partitioned table by >>> several concurrent sessions. > >> Yeah, I can reproduce it too. If I had to guess, I'd say it's another >> bug due to >> commit 3fb307bc4a76815f96fec28a0d1525ab3fbbcfb4 >> Author: Andres Freund >> Date: Mon Sep 9 05:21:30 2019 -0700 >> Reorder EPQ work, to fix rowmark related bugs and improve efficiency. >> which introduced relsubs_done et al, and perhaps did not get the life >> cycle / resetting right. Not sure. > > Yup, that's it exactly. EvalPlanQualStart was expecting to reuse > relsubs_rowmark and relsubs_done, but that storage will be recycled by > EvalPlanQualEnd because it's in the query context of the recheckestate. > AFAICS the re-use has no semantic value, so I just got rid of it. Sounds good, thank you! Regards, Oleksii “Alex” Kliukin
В списке pgsql-bugs по дате отправления
От: Tom Lane
Дата: