Re: Unexpected behaviour: it was documented to return the same value

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: KES <kes-kes(at)yandex(dot)ru>
Cc: "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-13 15:17:06
Message-ID: CAKFQuwbuLZf0TmWt5pUTOG0t+BY0DVO7TBXxgvU1fYD_ba0tGQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sunday, July 13, 2025, KES <kes-kes(at)yandex(dot)ru> wrote:

> I suppose that DEFAULT syntax should be used to set setting to its default
> value. Eg.
> set_config( 'my.option', DEFAULT, false )
> This is clear what should happen here. Also this syntax will correspond to
> other places, eg. INSERT INTO xx (name) VALUES (DEFAULT).
>
> Using NULL to set reset the value to the default is very very confusing.
> set_config( 'my.option', NULL, false )
> Expected: this call should make option unrecognizable again.
>

I don’t see us changing this even if someone were willing to write a
patch. You will have to make do with the behavior that exists.

David J.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2025-07-13 15:27:06 Re: please define 'statement' in the glossary
Previous Message Laurenz Albe 2025-07-13 14:58:57 Re: please define 'statement' in the glossary