Re: amcheck (B-Tree integrity checking tool)

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)
Date: 2016-09-02 18:16:04
Message-ID: CAM3SWZRL0w0ua8TxXanCYs=STPFXSiFSrdc=u4nMLTBjj9rxhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 2, 2016 at 11:11 AM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:
> I changed the CF entry to "Waiting on Author" pending that. (I was
> starting to review the patch for commit, so it's none to early to
> mention that the last posted version is not what I should be
> looking at.)

There are only tiny differences, which in any case you can see in the
commit log on Github. There is no reason why code review needs to
block on this V3, IMV.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2016-09-02 18:19:46 Re: amcheck (B-Tree integrity checking tool)
Previous Message Andres Freund 2016-09-02 18:16:01 Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)