Re: Parent/child context relation in pg_get_backend_memory_contexts()
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: torikoshia <torikoshia@oss.nttdata.com>
Cc: Melih Mutlu <m.melihmutlu@gmail.com>, Andres Freund <andres@anarazel.de>, Stephen Frost <sfrost@snowman.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-02-14T07:23:38Z
Lists: pgsql-hackers
On Fri, Jan 19, 2024 at 05:41:45PM +0900, torikoshia wrote: > We already have additional description below the table which explains each > column of the system view. For example pg_locks: > https://www.postgresql.org/docs/devel/view-pg-locks.html I was reading the patch, and using int[] as a representation of the path of context IDs up to the top-most parent looks a bit strange to me, with the relationship between each parent -> child being preserved, visibly, based on the order of the elements in this array made of temporary IDs compiled on-the-fly during the function execution. Am I the only one finding that a bit strange? Could it be better to use a different data type for this path and perhaps switch to the names of the contexts involved? It is possible to retrieve this information some WITH RECURSIVE as well, as mentioned upthread. Perhaps we could consider documenting these tricks? -- Michael
Commits
-
Add missing pointer dereference in pg_backend_memory_contexts view
- da87dc07f16e 18.0 landed
-
Add path column to pg_backend_memory_contexts view
- 32d3ed8165f8 18.0 landed
-
Allow memory contexts to have both fixed and variable ident strings.
- 442accc3fe0c 11.0 cited