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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
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 09:11:43
Message-ID: Z07LTy0EaSLleDs7@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 03, 2024 at 02:01:00PM +0530, Amit Kapila wrote:
> 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.

Sure. I've not seen anything else, but things are complicated enough
in this code that a path could always have been missed.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiro Ikeda 2024-12-03 09:23:11 Doc: clarify the log message level of the VERBOSE option
Previous Message Richard Guo 2024-12-03 08:56:17 Wrong results with right-semi-joins