Re: Enhancing Memory Context Statistics Reporting

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Rahila Syed <rahilasyed90@gmail.com>

Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2025-04-08T08:03:09Z

Lists: pgsql-hackers

> On 8 Apr 2025, at 07:40, Rahila Syed <rahilasyed90@gmail.com> wrote:

>  
>> > Renamed both to use MemoryContextReporting* namespace, which leaves
>> > MemoryContextReportingBackendState at an unwieldly long name.  I'm running out
>> > of ideas on how to improve and it does make purpose quite explicit at least.
>> 
>> How about
>> 
>> MemoryContextReportingBackendState -> MemoryStatsBackendState
>> MemoryContextReportingId -> MemoryStatsContextId
>> MemoryContextReportingSharedState -> MemoryStatsCtl
>> MemoryContextReportingStatsEntry -> MemoryStatsEntry
>  
> Fixed accordingly.

That's much better, thanks.

There was a bug in the shmem init function which caused it to fail on Windows,
the attached fixes that.

--
Daniel Gustafsson

Commits

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

Cross-check lists of built-in LWLock tranches.
- 2047ad068139 19 (unreleased) cited
Convert strncpy to strlcpy
- 45e7e8ca9e93 18.0 landed
Typo and doc fixups for memory context reporting
- f8c115a6cb65 18.0 landed
Add missing string terminator
- d2a1ed1727a8 18.0 landed
Rename argument in pg_get_process_memory_contexts().
- c57971034e69 18.0 landed
Add function to get memory context stats for processes
- 042a66291b04 18.0 landed