Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks
Date
Msg-id B9C7D975-8FD2-43AD-90DA-C83DD92AE6AC@yesql.se
Whole thread
In response to Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-hackers
> On 1 Apr 2026, at 17:36, Jacob Champion <jacob.champion@enterprisedb.com> wrote:
>
> On Wed, Apr 1, 2026 at 6:58 AM Andres Freund <andres@anarazel.de> wrote:
>> I'm afraid the guy maintaining both IPC::Run [1] and IO::Tty has gone all in on AI
>> authored code.  Both IPC::Run and IO::Tty have seen more merges in the last
>> week than in the 5 years before. Stuff getting merged left and right, with
>> failing tests to boot.
>>
>> If I wanted to do a supply chain attack on postgres, this would be the
>> way. Hijack IPC::Run, edit the commits locally on a committers machine before
>> push, to add a backdoor, celebrate.
>
> I did consider locking the exact version of IPC::Run during the NetBSD
> flake debacle [1], but abandoned it after the cross-platform pain... I
> believed signature verification was "good enough" at the time. Should
> we reconsider?

I think it makes sense to pin the versions of these modules, I personally have
them like that on my system to avoid surprises from package upgrades.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks
Next
From: Andres Freund
Date:
Subject: Re: AIO / read stream heuristics adjustments for index prefetching