Re: Commit fest 2017-11 - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Commit fest 2017-11
Date
Msg-id AD1095E6-9B9B-4A37-92B7-0A00F88773ED@yandex-team.ru
Whole thread Raw
In response to Re: Commit fest 2017-11  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Commit fest 2017-11  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael, thank you for your hard work!

> 30 нояб. 2017 г., в 10:39, Michael Paquier <michael.paquier@gmail.com> написал(а):
>
> On Thu, Nov 30, 2017 at 2:29 PM, Tsunakawa, Takayuki
> <tsunakawa.takay@jp.fujitsu.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
thenchange 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
Anastasiathat found drawback will be fixed before next CF. 

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

Best regards, Andrey Borodin.

pgsql-hackers by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Commit fest 2017-11
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions