Request a Demo
Home   >   mailing lists

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

From Robert Haas
Subject Re: Enhancing Memory Context Statistics Reporting
Date
Msg-id CA+TgmoZLJoXs-ZwuPQtYVpnt+JtiBZdM+K72mRutnTAzTssYdQ@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
Tree view 
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.

--
Robert Haas
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: harinath kanchu
Date:
Subject: [PATCH] Add permit_unlogged_tables GUC to control unlogged table creation.
Next
From: "David G. Johnston"
Date:
Subject: Re: [PATCH] Add permit_unlogged_tables GUC to control unlogged table creation.