Re: Bug in Configuration Setting Functions after a Commit

From: João felipe Chiarelli Bourscheid <joao(dot)felipe(dot)c(dot)b(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Bug in Configuration Setting Functions after a Commit
Date: 2025-02-24 18:49:33
Message-ID: CAKJNEkkSSQeP4VRE==zuyYb4ofZL4fBgpmNcjKqmdw5Ng2==PA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks, is there a way that I can help contrinuting to writing this into
the documentation? Should I refer to pgsql-docs(at)lists(dot)postgresql(dot)org ?

Em seg., 24 de fev. de 2025 15:38, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:

> On Mon, Feb 24, 2025 at 11:32 AM João felipe Chiarelli Bourscheid <
> joao(dot)felipe(dot)c(dot)b(at)gmail(dot)com> wrote:
>
>> The bug is the following: when I set a custom variable using the
>> configuration settings functions within a transaction, after I commit the
>> transaction, instead of the variable becoming null, it becomes an empty
>> string.
>>
>
> Yes, this is working as designed. The variable will never take on the
> null value, and the system won't forget that it exists once created, so the
> default value of empty string is restored when the transaction ends.
>
> There is some work-in-progress to clarify this in the documentation.
>
> David J.
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2025-02-24 18:56:55 Re: Bug in Configuration Setting Functions after a Commit
Previous Message David G. Johnston 2025-02-24 18:38:10 Re: Bug in Configuration Setting Functions after a Commit