| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: describe special values in GUC descriptions more consistently |
| Date: | 2025-02-11 22:41:51 |
| Message-ID: | 96FFD091-F221-4009-AA34-C740AC3C330D@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 11 Feb 2025, at 19:11, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> I thought about this one a bit, and I actually came to the opposite
> conclusion. IMHO it's reasonably obvious that an empty string means that
> the file isn't loaded, so there's not much point in stating it in the GUC
> description. Instead, I think we should follow the
> archive_command/archive_library example and use this space _only_ as a
> cross-reference to each other. There's certainly some nuances missed with
> this strategy, but that's not unique to this GUC.
I don't necessarily disagree with this, but the proposed wording makes it sound
sort of like users have to select one or the other. Could it be softened a
little like perhaps "An empty string disables, \"ssl_crl_foo\" is still used"?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-02-11 22:42:26 | Re: Track the amount of time waiting due to cost_delay |
| Previous Message | Tomas Vondra | 2025-02-11 22:33:45 | Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup |