Horton
Menu

Re: Enhancing Memory Context Statistics Reporting

Andres Freund <andres@anarazel.de>

View thread
From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Rahila Syed <rahilasyed90@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, torikoshia <torikoshia@oss.nttdata.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2026-01-13T21:47:41Z
Lists: 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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Cross-check lists of built-in LWLock tranches.

  2. Convert strncpy to strlcpy

  3. Typo and doc fixups for memory context reporting

  4. Add missing string terminator

  5. Rename argument in pg_get_process_memory_contexts().

  6. Add function to get memory context stats for processes