Re: Refactoring backend fork+exec code

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tristan Partin" <tristan(at)neon(dot)tech>
Cc: "Heikki Linnakangas" <hlinnaka(at)iki(dot)fi>, "Alexander Lakhin" <exclusion(at)gmail(dot)com>, "Andres Freund" <andres(at)anarazel(dot)de>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "Thomas Munro" <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Refactoring backend fork+exec code
Date: 2023-12-01 23:55:22
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

"Tristan Partin" <tristan(at)neon(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-12-02 00:00:50 Re: [Proposal] global sequence implemented by snowflake ID
Previous Message Nathan Bossart 2023-12-01 23:09:58 Re: Emitting JSON to file using COPY TO