|From:||Peter Geoghegan <pg(at)heroku(dot)com>|
|To:||Kevin Grittner <kgrittn(at)gmail(dot)com>|
|Cc:||Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>|
|Subject:||Re: amcheck (B-Tree integrity checking tool)|
|Views:||Raw Message | Whole Thread | Download mbox|
On Fri, Sep 2, 2016 at 11:19 AM, Kevin Grittner <kgrittn(at)gmail(dot)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.
Finally, the documentation was updated, to make it closer to the
Github project's documentation. I expanded what was started as the
original amcheck sgml documentation based on the experience of using
amcheck on production databases at Heroku. This isn't a big change,
but it's the biggest in V3. The documentation now emphasizes the
likelihood of amcheck finding software errors, which is all we found.
Jim Gray predicted that fault tolerant systems will tend to have
almost all problems arise from operator error and software faults in
practice, so perhaps I should have predicted that that would be the
|Next Message||Marko Tiikkaja||2016-09-07 18:49:25||Re: SELECT FOR UPDATE regression in 9.5|
|Previous Message||Andrew Borodin||2016-09-07 18:20:24||Re: GiST penalty functions [PoC]|