Re: Enhancing Memory Context Statistics Reporting

From: Rahila Syed <rahilasyed90(at)gmail(dot)com>
To: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: Enhancing Memory Context Statistics Reporting
Date: 2025-08-19 21:42:52
Message-ID: CAH2L28uL=Vm9E4Uf=tkg2Ki7_uDuAXORHVyCA7K_L=PAQ2p4sA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

=# select pg_get_process_memory_contexts(pg_backend_pid(), true, 1)
> from pg_stat_activity ;
>
> pg_get_process_memory_contexts
> --------------------------------
> (0 rows)
>
> Time: 6026.291 ms (00:06.026)
>
> Since v32 patch quickly returned the memory contexts as expected with
> the same parameter specified, there seems to be some degradation. Could
> you check it?
>

Thank you for reporting this failure. This issue was a regression caused by
the absence of a
ConditionVariableSignal() call in the summary = true code path,
which happened due to recent code refactoring.

PFA the fix.

Thank you,
Rahila Syed

Attachment Content-Type Size
v34-0001-Add-pg_get_process_memory_context-function.patch application/octet-stream 61.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-08-19 21:49:08 Re: fix comment for MAX_SIMUL_LWLOCKS
Previous Message Andres Freund 2025-08-19 21:40:23 Re: fix comment for MAX_SIMUL_LWLOCKS