| 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 17:57:12 |
| Message-ID: | CAM3SWZQdf2i89ezQUBfCYDP1WLQ0vDt8W-VNmeM2_NUPT5q=EQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 22, 2016 at 9:33 AM, David Steele <david(at)pgmasters(dot)net> wrote:
> It looks like an updated patch is expected here, though it seems that
> the only requests are for updates to comments.
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.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-22 18:32:17 | Re: amcheck (B-Tree integrity checking tool) |
| Previous Message | Fabrízio de Royes Mello | 2016-03-22 17:44:00 | Re: NOT EXIST for PREPARE |