Re: pg_amcheck contrib application

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(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-30 19:29:40
Message-ID: CA+TgmoZUONCkdcdR778EKuE+f1r5Obieu63db2OgMPHaEvEPTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 30, 2021 at 3:26 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> It looks mostly good to me. There is a off-by-one error introduced with:
>
> - else if (chunkno != (endchunk + 1))
> + else if (expected_chunk_seq < last_chunk_seq)
>
> I think that needs to be
>
> + else if (expected_chunk_seq <= last_chunk_seq)
>
> because otherwise it won't complain if the only missing chunk is the very last one.

OK, how about this version?

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

Attachment Content-Type Size
simply-remove-chunkno-concept-v4.patch application/octet-stream 6.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-04-30 19:29:57 Re: MaxOffsetNumber for Table AMs
Previous Message Mark Dilger 2021-04-30 19:26:36 Re: pg_amcheck contrib application