From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(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) |
Date: | 2016-03-22 18:32:17 |
Message-ID: | CAM3SWZS+bW91azqV2AeKziVsoaW7a4ydvsHRfsX4OjM0Ugub1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 22, 2016 at 10:57 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> That's right - I have a small number of feedback items to work
> through. I also determined myself that there could be a very low
> probability race condition when checking the key space across sibling
> pages, and will work to address that. If I'm right about that then
> it's not a lot of work to fix; I'm probably just going to use the
> right page's high key rather than its first data item.
I also want to use amcheck to test sorting, especially external
sorting which is currently totally untested. It would be nice to see
testing of strxfrm() on the buildfarm, too -- amcheck provides a nice
way to make sure strxfrm() and strcoll() are in agreement for at least
those cases that are tested, without having to worry about portability
in the same way as a simple pg_regress approach would require.
Note that there are reportedly systems in mainstream use where
strxfrm() is broken; it doesn't agree with strcoll().
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Grzegorz Sampolski | 2016-03-22 20:29:59 | Re: pam auth - add rhost item |
Previous Message | Peter Geoghegan | 2016-03-22 17:57:12 | Re: amcheck (B-Tree integrity checking tool) |