Re: Do we still need parent column in pg_backend_memory_context? - Mailing list pgsql-hackers

From David Rowley
Subject Re: Do we still need parent column in pg_backend_memory_context?
Date
Msg-id CAApHDvpCgTing_RPtaTs=wweAe7Kf43fQQ6bmRQHvmutKag-nw@mail.gmail.com
Whole thread Raw
In response to Re: Do we still need parent column in pg_backend_memory_context?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Do we still need parent column in pg_backend_memory_context?
List pgsql-hackers
On Wed, 31 Jul 2024 at 13:27, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> David Rowley <dgrowleyml@gmail.com> writes:
> > One thing we could do is remove it and see if anyone complains.  If we
> > did that today, there's about a year-long window for people to
> > complain where we could still reverse the decision.
>
> Seems like a plausible compromise.

Does anyone object to making this happen? i.e. remove
pg_backend_memory_contexts.parent column and see if anyone complains?

If nobody comes up with any reasons against it, then I propose making
this happen.

David



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Remove support for old realpath() API
Next
From: Michael Paquier
Date:
Subject: Instability with incremental backup tests (pg_combinebackup, 003_timeline.pl)