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

From Masahiko Sawada
Subject Re: Memory leak in WAL sender with pgoutput (v10~)
Date
Msg-id CAD21AoAC6D-ukdywA3nP5vuBW6M2qTGW4hV8JsyziVXJio0gDg@mail.gmail.com
Whole thread Raw
In response to Re: Memory leak in WAL sender with pgoutput (v10~)  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Thu, Dec 19, 2024 at 6:31 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Dec 19, 2024 at 09:27:04AM -0800, Masahiko Sawada wrote:
> > On Wed, Dec 18, 2024 at 6:26 PM Michael Paquier <michael@paquier.xyz> wrote:
> >> v2 does not have these weaknesses by design.
> >
> > I agree that v2 is better than v3 in terms of that.
>
> Okay.  In terms of the backbranches, would you prefer that I handle
> this patch myself as I have done the HEAD part?  This would need a
> second, closer, review but I could do that at the beginning of next
> week.

Thanks. Please proceed with this fix as you've already fixed the HEAD part.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Fix crash when non-creator being an iteration on shared radix tree
Next
From: Jeff Davis
Date:
Subject: Re: Speed up ICU case conversion by using ucasemap_utf8To*()