Re: Protect syscache from bloating with negative cache entries - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Protect syscache from bloating with negative cache entries
Date
Msg-id 20180703015036.3ifklp6sc26xuuey@alvherre.pgsql
Whole thread Raw
In response to Re: Protect syscache from bloating with negative cache entries  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: Protect syscache from bloating with negative cache entries  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 2018-Jul-02, Andrew Dunstan wrote:

> Andres suggested back in March (and again privately to me) that given how
> much this has changed from the original this CF item should be marked
> Returned With Feedback and the current patchset submitted as a new item.
> 
> Does anyone object to that course of action?

If doing that makes the "CF count" reset back to one for the new
submission, then I object to that course of action.  If we really
think this item does not belong into this commitfest, lets punt it to
the next one.  However, it seems rather strange to do so this early in
the cycle.  Is there really no small item that could be cherry-picked
from this series to be committed standalone?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Old small commitfest items
Next
From: Andres Freund
Date:
Subject: Re: Protect syscache from bloating with negative cache entries