Unexpected behaviour: it was documented to return the same value - Mailing list pgsql-docs

From PG Doc comments form
Subject Unexpected behaviour: it was documented to return the same value
Date
Msg-id 175175762761.3157502.18041595164515835428@wrigleys.postgresql.org
Whole thread Raw
Responses Re: Unexpected behaviour: it was documented to return the same value
List pgsql-docs
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/17/functions-admin.html
Description:

set_config ( setting_name text, new_value text, is_local boolean ) → text
Sets the parameter setting_name to new_value, and returns that value. If
is_local is true, the new value will only apply during the current
transaction. If you want the new value to apply for the rest of the current
session, use false instead. This function corresponds to the SQL command
SET.
set_config('log_statement_stats', 'off', false) → off
```
invoice=> select set_config( 'app.asdf', null, false ) is null;
 ?column?
----------
 f
(1 row)
invoice=> select set_config( 'app.asdf', null, false ) = '';
 ?column?
----------
 t
(1 row)
```
Expected: because I provided NULL value I expect to receive NULL as result
Actual: but function returns the empty string instead.
It would be better to follow documented behaviour, if it will not be
possible to fix it, please at least document that.
Thank you.

pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Missing File weather.txt
Next
From: "David G. Johnston"
Date:
Subject: Re: Unexpected behaviour: it was documented to return the same value