From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Joel Jacobson <joel(at)compiler(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: set_config() documentation clarification |
Date: | 2021-01-04 16:46:32 |
Message-ID: | CAKFQuwZe-wccYKouzFBcxL488jsQFNS2BO57qbUkVV9kw98-Pw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 4, 2021 at 8:26 AM Joel Jacobson <joel(at)compiler(dot)org> wrote:
> In the documentation at
> https://www.postgresql.org/docs/current/functions-admin.html
> this behaviour is not mentioned anywhere as far as I can see:
>
>
https://www.postgresql.org/docs/current/runtime-config-custom.html
I do think "Customized Options" is an accurate description. One needs to
consider their usage of such variables as "modular" even though there is no
library code involved. i.e., the description is possibly overly specific
but the variables created in this manner are simply namespaced but
otherwise usable in any manner you deem fit.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-01-04 17:09:39 | [PATCH]: Allow errors in parameter values to be reported during the BIND phase itself.. |
Previous Message | Victor Yegorov | 2021-01-04 16:28:11 | Re: Deleting older versions in unique indexes to avoid page splits |