Re: Concurrency bug in amcheck

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>
Subject: Re: Concurrency bug in amcheck
Date: 2020-08-04 23:17:48
Message-ID: CAPpHfds8atnrjHTOXoy30RmJBhZxK3-NO6DmzB82CECZqb=wqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 5, 2020 at 1:58 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Tue, Aug 4, 2020 at 7:27 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> > Thank you for your reminder. Revised patch is attached. Now, the contents of deleted btree pages isn't masked. I've checked that installcheck passes with wal_consistency_checking='Btree'. I'm going to push this if no objections.
>
> This looks good to me. One small thing, though: maybe the comments
> should not say anything about the REDO routine -- that seems like a
> case of "the tail wagging the dog" to me. Perhaps say something like:
>
> "Remove the last pivot tuple on the page. This keeps things simple
> for WAL consistency checking."

Pushed. Comment is changed as you suggested. But I've replaced "last
pivot tuple" with "remaining tuples", because the page can also have a
high key, which is also a tuple.

------
Regards,
Alexander Korotkov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-08-04 23:19:03 Re: Concurrency bug in amcheck
Previous Message Peter Geoghegan 2020-08-04 22:58:30 Re: Concurrency bug in amcheck