Re: Triage on old commitfest entries - Mailing list pgsql-hackers

From Jesper Pedersen
Subject Re: Triage on old commitfest entries
Date
Msg-id e1213cf1-6e7f-d1aa-ebea-481a0fa0e7df@redhat.com
Whole thread Raw
In response to Re: Triage on old commitfest entries  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
Hi,

On 10/3/21 16:18, Peter Geoghegan wrote:
>> Index Skip Scan 16
>>          Last substantive discussion 2021-05, currently passing cfbot
>>
>>          Seems possibly useful, but we're not making progress.
> This feature is definitely useful. My pet theory is that it hasn't
> made more progress because it requires expertise in two fairly
> distinct areas of the system. There is a lot of B-Tree stuff here,
> which is clearly my thing. But I know that I personally am much less
> likely to work on a patch that requires significant changes to the
> planner. Maybe this is a coordination problem.
>

I still believe that this is an important user-visible improvement.


However, there has been conflicting feedback on the necessary planner 
changes leading to doing double work in order to figure the best way 
forward.


Dmitry and Andy are doing a good job on keeping the patches current, but 
maybe there needs to be a firm decision from a committer on what the 
planner changes should look like before these patches can move forward.


So, is RfC the best state for that ?


Best regards,

  Jesper





pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Print error when libpq-refs-stamp fails
Next
From: Daniel Gustafsson
Date:
Subject: Re: 2021-09 Commitfest