Horton

Re: Creating a function for exposing memory usage of backend process

torikoshia <torikoshia@oss.nttdata.com>

View thread View on postgr.es
From: torikoshia <torikoshia@oss.nttdata.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, pgsql-hackers@postgresql.org
Date: 2020-07-01T13:18:01Z
Lists: pgsql-hackers 
On 2020-07-01 20:47, Daniel Gustafsson wrote:

> For the next version (if there will be one), please remove the 
> catversion bump
> from the patch as it will otherwise just break patch application 
> without
> constant rebasing (as it's done now).  The committer will handle the 
> catversion
> change if/when it gets committed.
> 
> cheers ./daniel

Thanks for telling me it!
I'll do that way next time.


Regards,

--
Atsushi Torikoshi
NTT DATA CORPORATION

Commits

  1. Add regression test for pg_backend_memory_contexts.

  2. Move codes for pg_backend_memory_contexts from mmgr/mcxt.c to adt/mcxtfuncs.c.

  3. Prevent non-superusers from reading pg_backend_memory_contexts, by default.

  4. Add pg_backend_memory_contexts system view.

  5. Fix yet another issue with step generation in partition pruning.