Commitb4f453f

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 parent7afca7e commitb4f453fCopy full SHA for b4f453f

File tree

-0

lines changed

-0

lines changed

Lines changed: 5 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -28576,6 +28576,11 @@ acl \| {postgres=arwdDxtm/postgres,foo=r/postgres}`
`28576`	`28576`	`use <literal>false</literal> instead. This function corresponds to`
`28577`	`28577`	`the SQL command <xref linkend="sql-set"/>.`
`28578`	`28578`	`</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>`
`28579`	`28584`	`<para>`
`28580`	`28585`	`<literal>set_config('log_statement_stats', 'off', false)</literal>`
`28581`	`28586`	`<returnvalue>off</returnvalue>`

Comments

(0)