From: Tom Lane <tgl@sss.pgh.pa.us>
To: KES <kes-kes@yandex.ru>
cc: "David G. Johnston" <david.g.johnston@gmail.com>,
        "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Subject: Re: Unexpected behaviour: it was documented to return the same value
In-reply-to: <47411752413203@mail.yandex.ru>
References: 
 <175175762761.3157502.18041595164515835428@wrigleys.postgresql.org>
 <CAKFQuwazjkoc-6sX2cWMVDtOUUZzO8BV39nEgvXjVUROaWOpoQ@mail.gmail.com>
 <CAKFQuwYYz5GWWwrEr5m=fuQHu6uGkc6qV4GzDZa5ps+nBp6CtA@mail.gmail.com>
 <47411752413203@mail.yandex.ru>
Comments: In-reply-to KES <kes-kes@yandex.ru>
	message dated "Sun, 13 Jul 2025 16:34:46 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <271343.1752421111.1@sss.pgh.pa.us>
Date: Sun, 13 Jul 2025 11:38:31 -0400
Message-ID: <271344.1752421111@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/271344.1752421111%40sss.pgh.pa.us>
Precedence: bulk

KES <kes-kes@yandex.ru> writes:
> I would prefer to remove the option from the configuration list
> instead of having it reset to empty string.

That is not the definition, and we'd be very unlikely to change
it to do that, because it would make no sense for built-in or
extension-defined settings.

			regards, tom lane