Re: pgsql: Avoid improbable PANIC during heap_update.
От | Peter Geoghegan |
---|---|
Тема | Re: pgsql: Avoid improbable PANIC during heap_update. |
Дата | |
Msg-id | CAH2-WznFSJs7UcO1yhTWiQHjYh4PYJULc3UXz+uftLVSNcUh-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Avoid improbable PANIC during heap_update. (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: pgsql: Avoid improbable PANIC during heap_update.
|
Список | pgsql-committers |
On Fri, Sep 30, 2022 at 5:09 PM Peter Geoghegan <pg@bowt.ie> wrote: > In any case we cannot really treat the information that we have about > that as a bug report -- not as things stand. Why should the question > of whether or not we ever set a page PD_ALL_VISIBLE without a cleanup > lock on v13 be a mystery at all? Why wouldn't a simple grep get to the > bottom of it? I have to imagine that the true explanation is very > simple and boring. I talked to Robins about this privately. I was wrong; there isn't a simple or boring explanation. Robins set out to find bugs like this in Postgres via stress-testing. He used a lab environment for this, and was quite methodical. So there is no reason to doubt that a PANIC happened on v13 at least once. There must be some relatively complicated explanation for that, but right now I can only speculate. -- Peter Geoghegan
В списке pgsql-committers по дате отправления: