agora inbox for pgsql-docs@postgresql.org  

help / color / mirror / Atom feed
From: KES <kes-kes@yandex.ru>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Unexpected behaviour: it was documented to return the same value
Date: Fri, 18 Jul 2025 12:28:50 +0300
Message-ID: <143981752830699@mail.yandex.ru> (raw)
In-Reply-To: <CAKFQuwbuLZf0TmWt5pUTOG0t+BY0DVO7TBXxgvU1fYD_ba0tGQ@mail.gmail.com>
References: <175175762761.3157502.18041595164515835428@wrigleys.postgresql.org>
	<CAKFQuwazjkoc-6sX2cWMVDtOUUZzO8BV39nEgvXjVUROaWOpoQ@mail.gmail.com>
	<CAKFQuwYYz5GWWwrEr5m=fuQHu6uGkc6qV4GzDZa5ps+nBp6CtA@mail.gmail.com>
	<47411752413203@mail.yandex.ru>
	<25341752413730@mail.yandex.ru>
	<CAKFQuwbuLZf0TmWt5pUTOG0t+BY0DVO7TBXxgvU1fYD_ba0tGQ@mail.gmail.com>

<div>Ok. Yes, changing the existing behaviour could lead to back compatibility issues.</div><div> </div><div>But have you found the functionality to "make an option unrecognizable again" useful? In theory, would it be appropriate to have eg. "UNSET" to perform that?</div><div><br /></div><div><br /></div><div>----------------</div>
                        <div>Кому: KES (kes-kes@yandex.ru);<br /></div>
                        <div>Копия: pgsql-docs@lists.postgresql.org;<br /></div>
                        <div>Тема: Unexpected behaviour: it was documented to return the same value;<br /></div>
                        <div>13.07.2025, 18:17, "David G. Johnston" &lt;david.g.johnston@gmail.com&gt;:<br /></div>
                        <blockquote>On Sunday, July 13, 2025, KES &lt;<a href="mailto:kes-kes@yandex.ru">kes-kes@yandex.ru</a>&gt; wrote:<br /><blockquote class="f13ca48719c8a60033905b23b39675agmail_quote" style="border-left-color:#ccc;border-left-style:solid;border-left-width:1px;margin:0 0 0 0.8ex;padding-left:1ex"><div>I suppose that DEFAULT syntax should be used to set setting to its default value. Eg.</div><div><div>set_config( 'my.option', DEFAULT, false )</div><div>This is clear what should happen here. Also this syntax will correspond to other places, eg. INSERT INTO xx (name) VALUES (DEFAULT).</div><div> </div><div>Using NULL to set reset the value to the default is very very confusing.</div><div><div>set_config( 'my.option', NULL, false )</div><div>Expected: this call should make option unrecognizable again.</div></div></div></blockquote><div><br /></div><div>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.</div><div><br /></div><div>David J.</div>
</blockquote>

view thread (8+ messages)

Message-ID: <143981752830699@mail.yandex.ru>
Permalink:  ../143981752830699@mail.yandex.ru/
Also on:    postgresql.org/message-id/143981752830699@mail.yandex.ru

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: kes-kes@yandex.ru, david.g.johnston@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Unexpected behaviour: it was documented to return the same value
  In-Reply-To: <143981752830699@mail.yandex.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox