| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, torikoshia <torikoshia(at)oss(dot)nttdata(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-07-15 10:46:15 |
| Message-ID: | CAApHDvrRtp0UoMyAkjnnb60jRvMN0bY1VtyeMy-ow_fXeSAawg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 13 Jul 2024 at 10:33, Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2024-07-15 10:47:14 | Re: New function normal_rand_array function to contrib/tablefunc. |
| Previous Message | David Rowley | 2024-07-15 10:43:56 | Re: Parent/child context relation in pg_get_backend_memory_contexts() |