| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | David Christensen <david(dot)christensen(at)crunchydata(dot)com> |
| Cc: | Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Proof of concept for GUC improvements |
| Date: | 2021-08-19 22:58:57 |
| Message-ID: | CAKFQuwaA=9CbEi_ZHm+W23A+4OErHviMCBQSVju56J2uML5TRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 19, 2021 at 3:44 PM David Christensen <
david(dot)christensen(at)crunchydata(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2021-08-19 23:10:37 | Re: RFC: Improve CPU cache locality of syscache searches |
| Previous Message | Zhihong Yu | 2021-08-19 22:47:33 | Re: [PATCH] Proof of concept for GUC improvements |