Horton

Re: Get memory contexts of an arbitrary backend process

Fujii Masao <masao.fujii@oss.nttdata.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Zhihong Yu <zyu@yugabyte.com>, torikoshia <torikoshia@oss.nttdata.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, gkokolatos@protonmail.com, kasahara.tatsuhito@gmail.com, Craig Ringer <craig@2ndquadrant.com>
Date: 2021-04-05T03:59:14Z
Lists: pgsql-hackers 

On 2021/04/05 12:20, Zhihong Yu wrote:
> +        * This is just a warning so a loop-through-resultset will not abort
> +        * if one backend logged its memory contexts during the run.
> 
> The pid given by arg 0 is not a PostgreSQL server process. Which other backend could it be ?

This is the comment that I added wrongly. So the comment should be
"This is just a warning so a loop-through-resultset will not abort
if one backend terminated on its own during the run.",
like pg_signal_backend(). Thought?

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Commits

  1. Add function to log the memory contexts of specified backend process.

  2. Add pg_backend_memory_contexts system view.

  3. Limit the verbosity of memory context statistics dumps.