Date: Tue, 31 Dec 2024 15:19:25 -0500
From: Roberto =?iso-8859-1?Q?C=2E_S=E1nchez?= <roberto@debian.org>
To: pgsql-hackers@lists.postgresql.org
Subject: Re: Backport of CVE-2024-10978 fix to older pgsql versions (11, 9.6,
 and 9.4)
Message-ID: <Z3RRzSHtAwaefAnj@localhost>
References: <3999105.1735610459@sss.pgh.pa.us>
 <Z3NHkW31MfTaV9u1@paquier.xyz>
 <Z3O-UihodQaydNhX@msg.df7cb.de>
 <Z3Qg5bDU3NnYW7AW@momjian.us>
 <Z3QmfWj8kmA2aFvI@localhost>
 <Z3RKHYoz1yFVDVj1@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <Z3RKHYoz1yFVDVj1@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/Z3RRzSHtAwaefAnj%40localhost>
Precedence: bulk

On Tue, Dec 31, 2024 at 02:46:37PM -0500, Bruce Momjian wrote:
> 
> Good question.  In a way, if the person who made the change sees your
> request and can answer it easily, it makes sense to ask.  However, I
> don't know the odds of that happening.
> 
> I would say ask, but don't take it personally if it your request is
> ignored.  We have fatigue about all the backpatching we have to do so it
> is hard to get motivated enough to research EOL branches.
> 
That's helpful feedback.

I definitely didn't take it personally this time and won't in the future
either.

My thinking was "ask once, bump the thread once after 2 or 3 weeks just
in case it got lost in the noise (this is a busy list), and after that
let the matter rest if there is no answer".

Regards,

-Roberto

-- 
Roberto C. Sánchez