Re: Visibility of a local variable

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Alejandro Burne <adburne(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Visibility of a local variable
Date: 2024-06-04 16:01:56
Message-ID: CAKFQuwYBxmU8kw6zrZXdwWP85Y6n3WkrBhaboBVPjg3EyPJHrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Monday, June 3, 2024, Alejandro Burne <adburne(at)gmail(dot)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.

Once a session knows a variable exists it cannot be made to not exist.
Only set back to its default empty string value (since custom variables are
only of type text)

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pierre Forstmann 2024-06-04 16:09:45 Re: BUG #18494: hstore data type not recognized by Npgsql in PostgreSQL 16.3
Previous Message SAS 2024-06-04 15:22:22 Minor update on pg_hba documentation