agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: KES <kes-kes@yandex.ru>
To: David G. Johnston <david.g.johnston@gmail.com>
To: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Unexpected behaviour: it was documented to return the same value
Date: Sun, 13 Jul 2025 16:34:46 +0300
Message-ID: <47411752413203@mail.yandex.ru> (raw)
In-Reply-To: <CAKFQuwYYz5GWWwrEr5m=fuQHu6uGkc6qV4GzDZa5ps+nBp6CtA@mail.gmail.com>
References: <175175762761.3157502.18041595164515835428@wrigleys.postgresql.org>
<CAKFQuwazjkoc-6sX2cWMVDtOUUZzO8BV39nEgvXjVUROaWOpoQ@mail.gmail.com>
<CAKFQuwYYz5GWWwrEr5m=fuQHu6uGkc6qV4GzDZa5ps+nBp6CtA@mail.gmail.com>
<div>I would prefer to remove the option from the configuration list instead of having it reset to empty string.</div><div> </div><div>Eg. set_config( 'my.option', NULL, false )</div><div> </div><div>Having it to return the empty string cause differences in the behaviour when parameter is not recognized at all and when it setup to default.</div><div> </div><div>How to make it "unrecognizable" again using set_config/RESET?</div><div> </div><div>The exact problem I am trying to resolve was asked here: https://stackoverflow.com/q/50923911/4632019</div><div> </div><div><br /></div><div><br /></div><div>----------------</div>
<div>Кому: kes-kes@yandex.ru (kes-kes@yandex.ru), pgsql-docs@lists.postgresql.org (pgsql-docs@lists.postgresql.org);<br /></div>
<div>Тема: Unexpected behaviour: it was documented to return the same value;<br /></div>
<div>07.07.2025, 17:40, "David G. Johnston" <david.g.johnston@gmail.com>:<br /></div>
<blockquote><div dir="ltr"><div dir="ltr"><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif"><span style="font-family:'arial' , 'helvetica' , sans-serif">On Mon, Jul 7, 2025 at 6:51 AM David G. Johnston <<a href="mailto:david.g.johnston@gmail.com">david.g.johnston@gmail.com</a>> wrote:</span></div></div><div class="f13ca48719c8a60033905b23b39675agmail_quote 5ec078e9233601eab4dccacd580e6022gmail_quote_container"><blockquote class="f13ca48719c8a60033905b23b39675agmail_quote" style="border-left-color:rgb( 204 , 204 , 204 );border-left-style:solid;border-left-width:1px;margin:0px 0px 0px 0.8ex;padding-left:1ex">On Saturday, July 5, 2025, PG Doc comments form <<a href="mailto:noreply@postgresql.org" target="_blank">noreply@postgresql.org</a>> wrote:<br /><blockquote class="f13ca48719c8a60033905b23b39675agmail_quote" style="border-left-color:rgb( 204 , 204 , 204 );border-left-style:solid;border-left-width:1px;margin:0px 0px 0px 0.8ex;padding-left:1ex">The following documentation comment has been logged on the website:<br />
<br />
Page: <a href="https://www.postgresql.org/docs/17/functions-admin.html"; target="_blank">https://www.postgresql.org/docs/17/functions-admin.html</a><br />
Description:<br /></blockquote></blockquote><div><br /></div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif">Yeah, this clarification just wasn't back-patched.</div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif"><br /></div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif"><a href="https://www.postgresql.org/docs/18/functions-admin.html#FUNCTIONS-ADMIN-SET">https://www.post... class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif"><br /></div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif">"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."</div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif"><br /></div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif">David J.</div><div class="81bf8e361cebb2c6d64fb4d6842d6ebgmail_default" style="font-family:'arial' , 'helvetica' , sans-serif"><br /></div></div></div>
</blockquote>
view thread (8+ messages) latest in thread
Message-ID: <47411752413203@mail.yandex.ru>
Permalink: ../47411752413203@mail.yandex.ru/
Also on: postgresql.org/message-id/47411752413203@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: <47411752413203@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