Re: pg_amcheck contrib application

From: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Amul Sul <sulamul(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_amcheck contrib application
Date: 2021-04-23 22:01:32
Message-ID: D3828900-5183-4C67-8A13-8D58E54570AA@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Apr 23, 2021, at 1:31 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> Perhaps something like this, closer to the way you had it?
>
> expected_size = chunk_seq < last_chunk_seq ? TOAST_MAX_CHUNK_SIZE
> : extsize - (last_chunk_seq * TOAST_MAX_CHUNK_SIZE);

It still suffers the same failures. I'll try to post something that accomplishes the changes to the reports that you are looking for.


Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-04-23 22:41:23 Re: PageGetItemIdCareful - should we MAXALIGN sizeof(BTPageOpaqueData)?
Previous Message Andres Freund 2021-04-23 20:43:06 Testing autovacuum wraparound (including failsafe)