Re: Extending amcheck to check toast size and compression

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Extending amcheck to check toast size and compression
Date: 2021-11-05 13:34:00
Message-ID: CA+TgmoYQ5Dirs9OCCbcmxOAf=CBmbgK35L0tP7RgeKySTx8JJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 4, 2021 at 6:58 PM Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> It only takes about 20 additional lines in the regression test to check the code paths for raw sizes which are too large and too small, so I've done that in this next version. Testing corrupt compressed data in a deterministic, cross platform manner 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-11-05 13:49:44 Re: removing global variable ThisTimeLineID
Previous Message Alvaro Herrera 2021-11-05 13:33:55 Re: pg14 psql broke \d datname.nspname.relname