Skip to content

Commit b4f453f

Browse files
committed
docs: Clarify that NULL arg to set_config() means reset to default
Author: David G. Johnston <david.g.johnston@gmail.com> Reviewed-by: Zhang Mingli <zmlpostgres@gmail.com> Discussion: https://www.postgresql.org/message-id/CAKFQuwY0SK6JdCci1VJX6xsztRXgGeVEY-grkENZx%2B3CZpyPcQ@mail.gmail.com
1 parent 7afca7e commit b4f453f

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

doc/src/sgml/func.sgml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28576,6 +28576,11 @@ acl | {postgres=arwdDxtm/postgres,foo=r/postgres}
2857628576
use <literal>false</literal> instead. This function corresponds to
2857728577
the SQL command <xref linkend="sql-set"/>.
2857828578
</para>
28579+
<para>
28580+
<function>set_config</function> accepts the NULL value for
28581+
<parameter>new_value</parameter>, but as settings cannot be null, it
28582+
is interpreted as a request to reset the setting to its default value.
28583+
</para>
2857928584
<para>
2858028585
<literal>set_config('log_statement_stats', 'off', false)</literal>
2858128586
<returnvalue>off</returnvalue>

0 commit comments

Comments
 (0)