RE: Memory leak in WAL sender with pgoutput (v10~) - Mailing list pgsql-hackers

From Zhijie Hou (Fujitsu)
Subject RE: Memory leak in WAL sender with pgoutput (v10~)
Date
Msg-id OS0PR01MB571640AB8FDA354CAB89066694312@OS0PR01MB5716.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Memory leak in WAL sender with pgoutput (v10~)  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Thursday, December 5, 2024 12:52 PM Michael Paquier <michael@paquier.xyz> wrote:

Hi,

>
> On Thu, Dec 05, 2024 at 04:31:56AM +0000, Zhijie Hou (Fujitsu) wrote:
> > I realized that this patch cannot be backpatched because it introduces
> > a new field into the public PGOutputData structure. Therefore, I think
> > we may need to use Alvaro's version [1] for the back branches.
> >
>
> Thanks for the patch.
>
> For HEAD it should be as good as it can be as it avoids the problem of
> CacheMemoryContext bloating for your case and my case.  Alvaro's patch
> would not take care of your case, unfortunately, but I'm less worried about this
> case in the back branches and we don't track the parent context where
> StartupDecodingContext() has begun its work when building PGOutputData.
> Thoughts?

I am fine with the plan. Thanks.

Best Regards,
Hou zj




pgsql-hackers by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: Use streaming read API in pgstattuple.
Next
From: Amit Langote
Date:
Subject: Re: generic plans and "initial" pruning