Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Date
Msg-id CAH2-WzkZUE3T97dtfvPB40Q4w7VyDJ9uLTXpF_Wbn8oaO_VEbA@mail.gmail.com
Whole thread Raw
In response to Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)  (Mark Dilger <mark.dilger@enterprisedb.com>)
List 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 by date:

Previous
From: Mark Dilger
Date:
Subject: Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Next
From: Ranier Vilela
Date:
Subject: [PATCH] Explicit null dereferenced (src/backend/access/heap/heaptoast.c)