Re: Concurrency bug in amcheck - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Concurrency bug in amcheck
Date
Msg-id CAPpHfds8atnrjHTOXoy30RmJBhZxK3-NO6DmzB82CECZqb=wqg@mail.gmail.com
Whole thread Raw
In response to Re: Concurrency bug in amcheck  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Concurrency bug in amcheck
List pgsql-hackers
On Wed, Aug 5, 2020 at 1:58 AM Peter Geoghegan <pg@bowt.ie> wrote:
> On Tue, Aug 4, 2020 at 7:27 AM Alexander Korotkov <aekorotkov@gmail.com> wrote:
> > Thank you for your reminder.   Revised patch is attached.  Now, the contents of deleted btree pages isn't masked.
I'vechecked 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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Concurrency bug in amcheck
Next
From: Peter Geoghegan
Date:
Subject: Re: Concurrency bug in amcheck