Re: Refactoring backend fork+exec code - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Refactoring backend fork+exec code
Date
Msg-id 266005.1701474922@sss.pgh.pa.us
Whole thread Raw
In response to Re: Refactoring backend fork+exec code  ("Tristan Partin" <tristan@neon.tech>)
List pgsql-hackers
"Tristan Partin" <tristan@neon.tech> writes:
> On Fri Dec 1, 2023 at 2:44 PM CST, Heikki Linnakangas wrote:
>> Committed a fix with memset(). I'm not sure what our policy with 
>> backpatching this kind of issues is. This goes back to all supported 
>> versions, but given the lack of complaints, I chose to not backpatch.

> Seems like a harmless think to backpatch. It is conceivable that someone 
> might want to run Valgrind on something other than HEAD.

FWIW, I agree with Heikki's conclusion.  EXEC_BACKEND on non-Windows
is already a niche developer-only setup, and given the lack of complaints,
nobody's that interested in running Valgrind with it.  Fixing it on HEAD
seems like plenty.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Emitting JSON to file using COPY TO
Next
From: Tomas Vondra
Date:
Subject: Re: [Proposal] global sequence implemented by snowflake ID