Postgres Pro
Downloads
Home   >   mailing lists

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-Wzm0STs+m=+KXRF7Nm6Uf=oibgb__EhCACvoW5E1t_G-BA@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>)
Responses Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
Tree view 
On Thu, Aug 27, 2020 at 4:57 PM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
> The amcheck patch has Asserts in hio.c that purport to disallow writing invalid header bits to disk.

Can it also be a runtime check for the verification process? I think
that we can easily afford to be fairly exhaustive about stuff like
this.

-- 
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Next
From: Tom Lane
Date:
Subject: Re: Clang Address Sanitizer (Postgres14) Detected Memory Leaks