Re: Patch to address creation of PgStat* contexts with null parent context - Mailing list pgsql-hackers

From Drouvot, Bertrand
Subject Re: Patch to address creation of PgStat* contexts with null parent context
Date
Msg-id b948b729-42fe-f88c-2f4a-0e65d84c049b@amazon.com
Whole thread Raw
In response to Re: Patch to address creation of PgStat* contexts with null parent context  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Patch to address creation of PgStat* contexts with null parent context
Re: Patch to address creation of PgStat* contexts with null parent context
List pgsql-hackers

Hi,

On 9/6/22 7:53 AM, Kyotaro Horiguchi wrote:
At Mon, 5 Sep 2022 14:46:55 +0200, "Drouvot, Bertrand" <bdrouvot@amazon.com> wrote in
Looks like that both approaches have their pros and cons. I'm tempted
to vote +1 on "just changing" the parent context to TopMemoryContext
and not changing the allocations locations.
Yeah. It is safe more than anything and we don't have a problem there.

So, I'm fine with just replacing the parent context at the three places.

Attached a patch proposal to do so.

Regards,
--

Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachment

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: [postgis-devel] PostGIS and json_categorize_type (Re: pgsql: Revert SQL/JSON features)
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE