| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
| Cc: | Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parent/child context relation in pg_get_backend_memory_contexts() |
| Date: | 2024-02-14 07:23:38 |
| Message-ID: | ZcxqerWx_jDZgtDQ@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2024-02-14 07:26:52 | About a recently-added message |
| Previous Message | Robert Haas | 2024-02-14 07:23:14 | Re: DSA_ALLOC_NO_OOM doesn't work |