| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(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:19:46 |
| Message-ID: | CACjxUsPjZu=n5_n67+sX246OTp-=V3K=iW41+775s00_LN0VQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 2, 2016 at 1:16 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> 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.
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.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-09-02 18:19:50 | Re: amcheck (B-Tree integrity checking tool) |
| Previous Message | Peter Geoghegan | 2016-09-02 18:16:04 | Re: amcheck (B-Tree integrity checking tool) |