| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | João felipe Chiarelli Bourscheid <joao(dot)felipe(dot)c(dot)b(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:38:10 |
| Message-ID: | CAKFQuwaWMy7NKqF4z3anLvvPbQRBGrtki4L5UmSziR5oo08yaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | João felipe Chiarelli Bourscheid | 2025-02-24 18:49:33 | Re: Bug in Configuration Setting Functions after a Commit |
| Previous Message | João felipe Chiarelli Bourscheid | 2025-02-24 18:26:07 | Bug in Configuration Setting Functions after a Commit |