| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | David Christensen <david(at)pgguru(dot)net>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Cary Huang <cary(dot)huang(at)highgo(dot)ca> |
| Subject: | Re: [PATCH] Proof of concept for GUC improvements |
| Date: | 2022-03-22 00:53:44 |
| Message-ID: | 2439960.1647910424@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> My impression is that there's not a lot of enthusiasm for the concept? If
> that's true we maybe ought to mark the CF entry as rejected?
Yeah, I'm kind of leaning that way too. I don't see how we can
incorporate the symbolic values into any existing display paths
without breaking applications that expect the old output.
That being the case, it seems like we'd have "two ways to do it"
indefinitely, which would add enough confusion that I'm not
sure there's a net gain. In particular, I foresee novice questions
along the lines of "I set foo to disabled, why is it showing
as zero?".
If we'd done it like this from the beginning, it'd have been
great, but retrofitting it now is a lot less appealing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-22 00:54:15 | Re: Reducing power consumption on idle servers |
| Previous Message | Andres Freund | 2022-03-22 00:52:41 | Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce) |