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

From Andres Freund
Subject Re: Enhancing Memory Context Statistics Reporting
Date
Msg-id o3n2sowv7cjzaha2vcavb7rb6locudyd2w7ajynrg54ktl42ox@pnc7zoc4f6yo
Whole thread Raw
In response to Re: Enhancing Memory Context Statistics Reporting  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

On 2026-01-13 16:11:24 -0500, Robert Haas wrote:
> On Tue, Jan 13, 2026 at 3:26 PM Andres Freund <andres@anarazel.de> wrote:
> > All the error handling paths (hopefully) have an LWLockReleaseAll()... Which
> > is pretty crucial given that we do stuff outside of transactions in other
> > places.
> >
> > That doesn't mean the other concerns about resource management are unfounded,
> > however.
> 
> Yeah, I actually wasn't completely sure about that particular comment.
> I think what will happen if we ERROR outside of a transaction is that
> it will become FATAL and kill the backend, but I'm not 100% positive
> about that.

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.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [PATCH] Add permit_unlogged_tables GUC to control unlogged table creation.
Next
From: Pierre
Date:
Subject: [PATCH] check kernel version for io_method