Re: Enhancing Memory Context Statistics Reporting - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Enhancing Memory Context Statistics Reporting
Date
Msg-id CA+TgmoZndbmJqDR9-qPbhJ-9e07CnLuLy6xzrtRnGmgeQaBg1A@mail.gmail.com
Whole thread Raw
In response to Re: Enhancing Memory Context Statistics Reporting  (Andres Freund <andres@anarazel.de>)
Responses Re: Enhancing Memory Context Statistics Reporting
List pgsql-hackers
On Tue, Jan 13, 2026 at 4:47 PM Andres Freund <andres@anarazel.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



pgsql-hackers by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: SQL:2023 JSON simplified accessor support
Next
From: Andres Freund
Date:
Subject: Re: Enhancing Memory Context Statistics Reporting