Re: Enhancing Memory Context Statistics Reporting

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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-13 20:26:02
Message-ID: ulzmfs7wuhon3ntyci3njk5w2soh45jtwhd4cokacn4fbfnazm@whrfe3yw3247
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2026-01-13 14:31:00 -0500, Robert Haas wrote:
> Also, it's not really safe to acquire an LWLock if there's no
> transaction active. If we error afterward, what will release the
> LWLock?

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.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-01-13 20:28:36 Re: Proposal: SELECT * EXCLUDE (...) command
Previous Message Sami Imseih 2026-01-13 20:24:51 Re: Cleaning up PREPARE query strings?