Re: amcheck (B-Tree integrity checking tool) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: amcheck (B-Tree integrity checking tool)
Date
Msg-id CAB7nPqTSR189Yn54Zh2msVoaRmg84Nbz=T+zcvJWtUUTK=bkYw@mail.gmail.com
Whole thread Raw
In response to Re: amcheck (B-Tree integrity checking tool)  (Peter Geoghegan <pg@heroku.com>)
Responses Re: amcheck (B-Tree integrity checking tool)  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Thu, Sep 8, 2016 at 3:44 AM, Peter Geoghegan <pg@heroku.com> wrote:
> On Fri, Sep 2, 2016 at 11:19 AM, Kevin Grittner <kgrittn@gmail.com> wrote:
>> IMV the process is to post a patch to this list to certify that it
>> is yours to contribute and free of IP encumbrances that would
>> prevent us from using it.  I will wait for that post.
>
> I attach my V3. There are only very minor code changes here, such as
> breaking out a separate elevel constant for DEBUG2 traces that show
> information of how the B-Tree is accessed (e.g. current level, block
> number). Tiny tweaks to about 3 comments were also performed. These
> changes are trivial.
>
> I've also removed the tests added, since external sort regression test
> coverage is in a much better place now.

Okay, moved to next CF. I may look at it finally I got some use-cases
for it, similar to yours I guess..
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: multivariate statistics (v19)
Next
From: Michael Paquier
Date:
Subject: Re: PoC: Partial sort