From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Removing "Included attributes in B-tree indexes" section from docs |
Date: | 2018-06-18 20:34:07 |
Message-ID: | 67eba2bf-312c-f144-c97d-57e51b3e23d3@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/18/2018 01:31 PM, Andres Freund wrote:
> On 2018-06-18 13:21:43 -0400, Alvaro Herrera wrote:
>> On 2018-Jun-17, Peter Geoghegan wrote:
>>
>>> On Sat, Jun 16, 2018 at 8:51 PM, Alvaro Herrera
>>> <alvherre(at)2ndquadrant(dot)com> wrote:
>>>> I don't necessarily object to the proposed change, but I think you
>>>> should generally wait a bit longer for others to react.
>>> What wait period do you think is appropriate in this case?
>> One which includes at least half a working day in a different timezone.
>> You asked mid-afternoon on a Friday in a timezone pretty far west. I
>> think you could find people in their offices in Easter Island, but not
>> many more.
> I think there's also a question of how much a patch is blocking you /
> others. A shorter question period is more understandable if it's step
> 3/40, rather than 1/1...
>
Yeah, but this would still apply for the first in a series of advertised
patches.
I usually try to wait at least a couple of days. I'm sure every
committer understands how you can feel the itch to push. I know I do.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robbie Harwood | 2018-06-18 20:34:43 | Re: libpq compression |
Previous Message | Andrew Dunstan | 2018-06-18 20:20:07 | Re: Index Skip Scan |