Re: [PATCH] Proof of concept for GUC improvements - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: [PATCH] Proof of concept for GUC improvements
Date
Msg-id CAKFQuwaA=9CbEi_ZHm+W23A+4OErHviMCBQSVju56J2uML5TRg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Proof of concept for GUC improvements  (David Christensen <david.christensen@crunchydata.com>)
Responses Re: [PATCH] Proof of concept for GUC improvements  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, Aug 19, 2021 at 3:44 PM David Christensen <david.christensen@crunchydata.com> wrote: 
Functionality-wise, any thoughts on the overall approach or the specific patch?

If this information was exposed only by an addition to pg_settings, and thus not changeable via a GUC or affecting SHOW, I think it would be more likely to get accepted.  Being more liberal in the accepting of these values as input seems less problematic so that aspect could just stay.  But the display changes should be done with new outputs, not repurposing existing ones.

I'm at -0.5 as to whether such a patch would actually be an improvement or whether the added possibilities would just be confusing and, because it is all optional, indefinitely so.

David J.

pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: [PATCH] Proof of concept for GUC improvements
Next
From: John Naylor
Date:
Subject: Re: RFC: Improve CPU cache locality of syscache searches