Horton

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

Kasahara Tatsuhito <kasahara.tatsuhito@gmail.com>

View thread View on postgr.es
From: Kasahara Tatsuhito <kasahara.tatsuhito@gmail.com>
To: pgsql-hackers@lists.postgresql.org
Cc: Fujii Masao <masao.fujii@gmail.com>, atsushi torikoshi <atorik@gmail.com>
Date: 2020-08-07T07:38:13Z
Lists: pgsql-hackers 
The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           not tested
Documentation:            tested, passed

I tested the latest patch(0007-Adding-a-function-exposing-memory-usage-of-local-backend.patch) 
with the latest PG-version (199cec9779504c08aaa8159c6308283156547409) and test was passed.
It looks good to me.

The new status of this patch is: Ready for Committer

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.