Re: Commit fest 2017-11

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commit fest 2017-11
Date: 2017-11-30 05:53:47
Message-ID: AD1095E6-9B9B-4A37-92B7-0A00F88773ED@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael, thank you for your hard work!

> 30 нояб. 2017 г., в 10:39, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> написал(а):
>
> On Thu, Nov 30, 2017 at 2:29 PM, Tsunakawa, Takayuki
> <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
>> Now I tried that, successfully marking it as "waiting on author", but the patch doesn't move to the next CF when I then change the status as "Move to next CF." How can I move the patch to next CF?
>
> If you have a patch "waiting on author" that you would like to move to
> the next commit fest, just switch its status back temporarily to
> "needs review", and then do the move. Yes, that's unnecessary
> complication but I am not going to fight against the design of the CF
> app.

I want to move also "Covering B-tree indexes (aka INCLUDE)" . Seems like we have common view with Peter Geoghegan and Anastasia that found drawback will be fixed before next CF.

If there is no objections, I'll put "needs review" to move.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-11-30 05:54:50 Re: [HACKERS] logical decoding of two-phase transactions
Previous Message Tsunakawa, Takayuki 2017-11-30 05:46:46 RE: Commit fest 2017-11