public inbox for [email protected]
help / color / mirror / Atom feedFrom: Amit Kapila <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Postgres hackers <[email protected]>
Subject: Re: Memory leak in WAL sender with pgoutput (v10~)
Date: Tue, 3 Dec 2024 14:01:00 +0530
Message-ID: <CAA4eK1+-jNguD8j6ezGXVZM_hdwaahXPpT0816Zi3ePaJGQgew@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CAA4eK1JMuOni-s5ZX1ahWZJLtOJbzbBsXZ8LiBPV_LN=736xEQ@mail.gmail.com>
<[email protected]>
<CAA4eK1LPDBqTjJMH5kowHq+NExR1vLecAweVEzNSONrsqCc2KQ@mail.gmail.com>
<[email protected]>
On Tue, Dec 3, 2024 at 12:17 PM Michael Paquier <[email protected]> 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.
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Memory leak in WAL sender with pgoutput (v10~)
In-Reply-To: <CAA4eK1+-jNguD8j6ezGXVZM_hdwaahXPpT0816Zi3ePaJGQgew@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox