Re: pgsql: Add function to get memory context stats for processes
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Daniel Gustafsson <dgustafsson@postgresql.org>,
Andres Freund <andres@anarazel.de>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Rahila Syed <rahilasyed90@gmail.com>
Date: 2025-04-23T18:14:34Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > My primary concern about the patch is that > ProcessGetMemoryContextInterrupt() can be called from any > CHECK_FOR_INTERRUPTS() and calls lots of DSA functions, including > dsa_create() and, via PublishMemoryContext(), dsa_allocate0(). I'm > shocked to hear that you and Andres think that's safe to do at any > current or future CHECK_FOR_INTERRUPTS() anywhere in the code; but > Andres seems very confident that it's fine, so perhaps I should just > stop worrying and be happy that we have the feature. Just for the record, it sounds quite unsafe to me too. I could credit it being all right to examine the process' MemoryContext data structures, but calling dsa_create() from CFI seems really insane. Way too many moving parts there. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Rename global variable backing DSA area
- 55ef7abf88c0 18.0 landed
-
Add function to get memory context stats for processes
- 042a66291b04 18.0 cited