| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "jens(dot)troeger(at)light-speed(dot)de" <jens(dot)troeger(at)light-speed(dot)de>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Please clarify docs on user-defined settings for SET and RESET |
| Date: | 2025-04-22 13:47:42 |
| Message-ID: | CAKFQuwa2FOM+W_UM6+ZbCPuKwqe832YZ6BgeU2pobv3Sw0hACQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Monday, April 21, 2025, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
>
>
> It seems that the assumed/implied default value for settings that did not
> exist for a session is the empty string? It would be useful to document
> that
> behavior explicitly.
This is presently being worked on. Some changes have made it into the v18
docs already.
>
> Furthermore, it seems impossible to actually *remove* such a user defined
> settings completely, correct? That too, I miss stated explicitly in the
> documentation.
>
Correct. The null is not the value of the setting, it is being provided
instead of producing a “setting does not exist” error.
The system never forgets a setting once set (within a session). Reset
restores a setting to its default value, which for text is the empty string.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-04-23 06:53:54 | Remove unnecessary secondary index terms for replication settings |
| Previous Message | PG Doc comments form | 2025-04-22 05:57:23 | Please clarify docs on user-defined settings for SET and RESET |