From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Alejandro Burne <adburne@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Visibility of a local variable
Date: Tue, 04 Jun 2024 13:05:57 -0400
Message-ID: <479909.1717520757@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwYBxmU8kw6zrZXdwWP85Y6n3WkrBhaboBVPjg3EyPJHrw@mail.gmail.com>
References: <CAOKeeVj8s0DcjcTUULEOXGB3Ro7ZmwcV=O-wX44Aqdx7BQo1TA@mail.gmail.com>
<CAKFQuwYBxmU8kw6zrZXdwWP85Y6n3WkrBhaboBVPjg3EyPJHrw@mail.gmail.com>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Monday, June 3, 2024, Alejandro Burne <adburne@gmail.com> wrote:
>> A local variable, created within a transaction, continues to persist
>> (without value) after the transaction has ended.
> This is under-documented but at present there is no plan to change this
> long-standing behavior, just document it better.
Keep in mind that this entire behavior (ie the ability to create GUCs
not declared in the C code) is an undocumented abuse of the GUC
system. We probably can't get rid of it at this late date, but
we're very unlikely to make any incompatible changes in the behavior.
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, david.g.johnston@gmail.com, adburne@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Visibility of a local variable
In-Reply-To: <479909.1717520757@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