Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzP3q-0007TP-PW for pgsql-hackers@arkaria.postgresql.org; Wed, 17 May 2023 21:51:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzP3p-0007NS-Py for pgsql-hackers@arkaria.postgresql.org; Wed, 17 May 2023 21:51:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzP3p-0007NJ-GU for pgsql-hackers@lists.postgresql.org; Wed, 17 May 2023 21:51:53 +0000 Received: from relay4-d.mail.gandi.net ([2001:4b98:dc4:8::224]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pzP3k-000NRg-J6 for pgsql-hackers@lists.postgresql.org; Wed, 17 May 2023 21:51:52 +0000 Received: (Authenticated sender: adsend@dunslane.net) by mail.gandi.net (Postfix) with ESMTPSA id B497CE0002; Wed, 17 May 2023 21:51:42 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------tER3HcOr0SIYn3UC5Ta60kYg" Message-ID: <32cf5bd7-da7f-27ef-a7cf-4e5505b28cc5@dunslane.net> Date: Wed, 17 May 2023 17:51:41 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: issue with meson builds on msys2 Content-Language: en-US To: Andres Freund Cc: Tom Lane , pgsql-hackers@lists.postgresql.org References: <20230427221828.2qo7z4xb4f7islln@awork3.anarazel.de> <236c0354-62b1-0ae1-a252-4c866bc1c5d6@dunslane.net> <20230504235413.eibaxlxslo76ipjl@awork3.anarazel.de> <2ff71af4-cdee-37b8-525a-2b25afd1769a@dunslane.net> <20230515193817.ttx4qf3ceqeufls2@awork3.anarazel.de> <26b0ebdb-3e7c-d562-620d-8e2f17286ff9@dunslane.net> <20230515201326.tbjgfdef6ul6oqfd@awork3.anarazel.de> <20230515223028.gkctmcoe7jtd5mmw@awork3.anarazel.de> <20230515234356.7ysq7w6jjsofeunt@awork3.anarazel.de> <20230516215200.wau4yfdpro3idlyv@awork3.anarazel.de> From: Andrew Dunstan In-Reply-To: <20230516215200.wau4yfdpro3idlyv@awork3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------tER3HcOr0SIYn3UC5Ta60kYg Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2023-05-16 Tu 17:52, Andres Freund wrote: > >> I suppose the alternative would be to change the way the buildfarm calls >> pg_ctl stop. Do you have a concrete suggestion for that? > The easiest fix is to redirect stdin to /dev/null (or some file, if that's > easier to do portably) - that should fix the problem entirely, without needing > IPC::Run. > Should only be needed for the start command, right? I can probably just add "< $devnull" to the command. I'll test it out. cheers andrew -- Andrew Dunstan EDB:https://www.enterprisedb.com --------------tER3HcOr0SIYn3UC5Ta60kYg Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit


On 2023-05-16 Tu 17:52, Andres Freund wrote:

I suppose the alternative would be to change the way the buildfarm calls
pg_ctl stop. Do you have a concrete suggestion for that?
The easiest fix is to redirect stdin to /dev/null (or some file, if that's
easier to do portably) - that should fix the problem entirely, without needing
IPC::Run.


Should only be needed for the start command, right? I can probably just add "< $devnull" to the command. I'll test it out.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com
--------------tER3HcOr0SIYn3UC5Ta60kYg--