| 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:56:55 |
| Message-ID: | CAKFQuwZ-WqweiYtLHnhjvuPRjAKGCsiWJ=p+eyXtYaufwJCbFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Feb 24, 2025 at 11:49 AM João felipe Chiarelli Bourscheid <
joao(dot)felipe(dot)c(dot)b(at)gmail(dot)com> wrote:
> 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 ?
>
I have targeted commitfest entry for this issue here:
https://commitfest.postgresql.org/patch/5548/
And a larger rework regarding NULL here that covers this topic briefly
since it is a bit unintuitive that settings may not take on a null value;
while current_setting can return NULL as an error-substitute sentinel value.
https://commitfest.postgresql.org/patch/5086/
Reviewing them would be very helpful.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kashaela Ransaw | 2025-02-25 01:41:48 | Re: error -10825 |
| Previous Message | João felipe Chiarelli Bourscheid | 2025-02-24 18:49:33 | Re: Bug in Configuration Setting Functions after a Commit |