Re: Extending amcheck to check toast size and compression - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Extending amcheck to check toast size and compression
Date
Msg-id CA+TgmoYQ5Dirs9OCCbcmxOAf=CBmbgK35L0tP7RgeKySTx8JJQ@mail.gmail.com
Whole thread Raw
In response to Re: Extending amcheck to check toast size and compression  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: Extending amcheck to check toast size and compression
List pgsql-hackers
On Thu, Nov 4, 2021 at 6:58 PM Mark Dilger <mark.dilger@enterprisedb.com> wrote:
> It only takes about 20 additional lines in the regression test to check the code paths for raw sizes which are too
largeand too small, so I've done that in this next version.  Testing corrupt compressed data in a deterministic, cross
platformmanner with a compact, easy to maintain regression test has eluded me and is not included here. 

OK, I've committed this version.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname
Next
From: Alvaro Herrera
Date:
Subject: Re: removing global variable ThisTimeLineID