Horton

Re: Parent/child context relation in pg_get_backend_memory_contexts()

David Rowley <dgrowleyml@gmail.com>

View thread View on postgr.es
From: David Rowley <dgrowleyml@gmail.com>
To: Melih Mutlu <m.melihmutlu@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael@paquier.xyz>, torikoshia <torikoshia@oss.nttdata.com>, Andres Freund <andres@anarazel.de>, Stephen Frost <sfrost@snowman.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-07-15T10:46:15Z
Lists: pgsql-hackers 
On Sat, 13 Jul 2024 at 10:33, Melih Mutlu <m.melihmutlu@gmail.com> wrote:
> I've been also thinking if we should still have the parent column, as finding out the parent is also possible via looking into the path. What do you think?

I think we should probably consider removing it. Let's think about
that later. I don't think its existence is blocking us from
progressing here.

David

Commits

  1. Add missing pointer dereference in pg_backend_memory_contexts view

  2. Add path column to pg_backend_memory_contexts view

  3. Allow memory contexts to have both fixed and variable ident strings.