Re: set_config with is_local parameter true escapes transaction boundaries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ruslan Talpa <ruslan(dot)talpa(at)subzero(dot)cloud>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: set_config with is_local parameter true escapes transaction boundaries
Date: 2023-01-11 00:39:06
Message-ID: 392925.1673397546@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ruslan Talpa <ruslan(dot)talpa(at)subzero(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2023-01-11 06:03:02 Re: pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records,
Previous Message Tom Lane 2023-01-10 22:21:27 Re: [OT] Microsoft: Kubernetes clusters hacked in malware campaign via PostgreSQL