Re: Bug in Configuration Setting Functions after a Commit
| От | João felipe Chiarelli Bourscheid |
|---|---|
| Тема | Re: Bug in Configuration Setting Functions after a Commit |
| Дата | |
| Msg-id | CAKJNEkkSSQeP4VRE==zuyYb4ofZL4fBgpmNcjKqmdw5Ng2==PA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Bug in Configuration Setting Functions after a Commit ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Список | pgsql-bugs |
Thanks, is there a way that I can help contrinuting to writing this into the documentation? Should I refer to pgsql-docs@lists.postgresql.org ?
Em seg., 24 de fev. de 2025 15:38, David G. Johnston <david.g.johnston@gmail.com> escreveu:
On Mon, Feb 24, 2025 at 11:32 AM João felipe Chiarelli Bourscheid <joao.felipe.c.b@gmail.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.
В списке pgsql-bugs по дате отправления: