Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Дата
Msg-id CAH2-WzkZUE3T97dtfvPB40Q4w7VyDJ9uLTXpF_Wbn8oaO_VEbA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)  (Mark Dilger <mark.dilger@enterprisedb.com>)
Список pgsql-hackers
On Thu, Aug 27, 2020 at 5:06 PM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
> These two are both checked in verify_heapam.c.  The point is that the system will also refuse to write out pages that
havethis corruption.  The Asserts could be converted to panics or whatever, but that has other more serious
consequences. Did you have something else in mind? 

Oh, I see -- you propose to add both an assert to hio.c, as well as a
check to amcheck itself. That seems like the right thing to do.

Thanks

--
Peter Geoghegan



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

Предыдущее
От: Mark Dilger
Дата:
Сообщение: Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Следующее
От: Ranier Vilela
Дата:
Сообщение: [PATCH] Explicit null dereferenced (src/backend/access/heap/heaptoast.c)