| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enhancing Memory Context Statistics Reporting |
| Date: | 2026-01-14 13:26:24 |
| Message-ID: | CA+TgmoZndbmJqDR9-qPbhJ-9e07CnLuLy6xzrtRnGmgeQaBg1A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 13, 2026 at 4:47 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm pretty sure that doesn't generally happen. There's promotion to FATAL if
> the top-level sigsetjmp() hasn't yet run (c.f. the check for
> PG_exception_stack in errstart()), but once it has been reached, it stays
> configured.
All right, then I guess I don't fully understand how the
error-outside-of-a-transaction case is handled. But I still think that
code like this needs to run in a transaction to avoid unexpected and
undesirable results. Do you see it differently?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-01-14 13:32:36 | Re: Enhancing Memory Context Statistics Reporting |
| Previous Message | Kirill Reshke | 2026-01-14 13:04:31 | Re: SQL:2023 JSON simplified accessor support |