From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ruslan Talpa <ruslan.talpa@subzero.cloud>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: set_config with is_local parameter true escapes transaction boundaries
Date: Tue, 10 Jan 2023 19:39:06 -0500
Message-ID: <392925.1673397546@sss.pgh.pa.us> (raw)
In-Reply-To: <997A11B3-BC14-44FB-A505-BE7C49BE5330@subzero.cloud>
References: <997A11B3-BC14-44FB-A505-BE7C49BE5330@subzero.cloud>
Ruslan Talpa <ruslan.talpa@subzero.cloud> writes:
> When executing set_config with the parameter ‘is_local’ set to true within a transaction, it is expected that the config value is not available after the transaction however once the config is set in any transaction, current_setting will return an empty string instead of null
The GUC infrastructure doesn't recognize null as a value, so you
are making a distinction that the system doesn't.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, ruslan.talpa@subzero.cloud, pgsql-bugs@lists.postgresql.org
Subject: Re: set_config with is_local parameter true escapes transaction boundaries
In-Reply-To: <392925.1673397546@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox