| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "kes-kes(at)yandex(dot)ru" <kes-kes(at)yandex(dot)ru>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unexpected behaviour: it was documented to return the same value |
| Date: | 2025-07-07 14:39:21 |
| Message-ID: | CAKFQuwYYz5GWWwrEr5m=fuQHu6uGkc6qV4GzDZa5ps+nBp6CtA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Jul 7, 2025 at 6:51 AM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Saturday, July 5, 2025, PG Doc comments form <noreply(at)postgresql(dot)org>
> wrote:
>
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/17/functions-admin.html
>> Description:
>>
>
Yeah, this clarification just wasn't back-patched.
https://www.postgresql.org/docs/18/functions-admin.html#FUNCTIONS-ADMIN-SET
"set_config accepts the NULL value for new_value, but as settings cannot be
null, it is interpreted as a request to reset the setting to its default
value."
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2025-07-09 12:06:33 | correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html |
| Previous Message | David G. Johnston | 2025-07-07 13:51:19 | Re: Unexpected behaviour: it was documented to return the same value |