Re: Memory leak in WAL sender with pgoutput (v10~)

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Memory leak in WAL sender with pgoutput (v10~)
Date: 2024-12-03 08:31:00
Message-ID: CAA4eK1+-jNguD8j6ezGXVZM_hdwaahXPpT0816Zi3ePaJGQgew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 3, 2024 at 12:17 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> So how about the attached that introduces a FreePublication() matching
> with GetPublication(), used to do the cleanup? Feel free to comment.
>

As you would have noted I am fine with the fix on these lines but I
suggest holding it till we conclude the memory context point raised by
me today. It is possible that we are still leaking some memory in
other related scenarios.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2024-12-03 08:33:19 Re: An inefficient query caused by unnecessary PlaceHolderVar
Previous Message Amit Kapila 2024-12-03 08:27:35 Re: Memory leak in WAL sender with pgoutput (v10~)