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

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

On Tue, Dec 03, 2024 at 08:49:41AM +0100, Alvaro Herrera wrote:
> That cannot be backpatched, though.

Extra code churn is always annoying across stable branches, so I'd
rather avoid it if we can.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2024-12-03 07:58:36 Re: Collation & ctype method table, and extension hooks
Previous Message Alvaro Herrera 2024-12-03 07:49:41 Re: Memory leak in WAL sender with pgoutput (v10~)