Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jeremy Schneider <schnjere(at)amazon(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Date: 2020-08-27 23:58:59
Message-ID: CAH2-Wzm0STs+m=+KXRF7Nm6Uf=oibgb__EhCACvoW5E1t_G-BA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 27, 2020 at 4:57 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-08-28 00:00:40 Re: Clang Address Sanitizer (Postgres14) Detected Memory Leaks
Previous Message Mark Dilger 2020-08-27 23:57:15 Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)