Re: Patch to address creation of PgStat* contexts with null parent context

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: reid(dot)thompson(at)crunchydata(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Patch to address creation of PgStat* contexts with null parent context
Date: 2022-08-05 08:40:01
Message-ID: 20220805.174001.172831392189505144.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Fri, 05 Aug 2022 17:22:38 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> Thus I thought that we may let pgstat_initialize() promptly allocate
> the memory.
>
> Does it make sense?
>
>
> About the patch, I had something like the attached in my mind.

I haven't fully checked, but this change might cause all other calls
to CreateCacheMemoryContext useless.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message wangw.fnst@fujitsu.com 2022-08-05 09:06:49 RE: Data is copied twice when specifying both child and parent table in publication
Previous Message Etsuro Fujita 2022-08-05 08:36:22 Re: postgres_fdw: batch inserts vs. before row triggers