Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rna1E-00DzFQ-3Y for pgsql-bugs@arkaria.postgresql.org; Fri, 22 Mar 2024 08:12:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rna1C-001Fef-MP for pgsql-bugs@arkaria.postgresql.org; Fri, 22 Mar 2024 08:12:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rna1C-001FeX-Eu for pgsql-bugs@lists.postgresql.org; Fri, 22 Mar 2024 08:12:50 +0000 Received: from dd25110.kasserver.com ([85.13.146.49]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rna1A-005ruu-L8 for pgsql-bugs@lists.postgresql.org; Fri, 22 Mar 2024 08:12:50 +0000 Received: from [192.168.0.101] (ip-037-201-153-175.um10.pools.vodafone-ip.de [37.201.153.175]) by dd25110.kasserver.com (Postfix) with ESMTPSA id BA596E1A0159; Fri, 22 Mar 2024 09:12:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technowledgy.de; s=kas202308201259; t=1711095168; bh=GSZA7UFyISDn6EsvLJrGQeNKk9Cava0bF7+fWFXoW1Q=; h=Date:From:Subject:To:Cc:References:In-Reply-To:From; b=FAaFE5eWiKx4oxezGp/wQiMI6eNLzlEh3wnh6TJiZx/xZj0ABqoWkJR+5jNjXOqRj kqzCwE5hqwBncwe0tmO1qdyZMTMtpnGgaF/bHMAH9PvT+hTkPChNs5OaDdqAicBUjD wPunM7e1TOeP54o2lHqim+wcKQbLvPA7lk+WqKP4b8EeeJvu9V/gLeVjRM5wcUR6VQ E6fzcMWqYpISYUtXkJSVuO2wU8dxsNNnXVzQahCPMEmoAS1QiZG++xsjeiKmTgWmt0 Kw0oofjTsX2+pIIIdJJpY/D4Yj//tl52RZg3mUUkiG8Dg6QyuPwXRfHS6O6TdNEzSe YpYNIti1/5K4g== Message-ID: Date: Fri, 22 Mar 2024 09:12:47 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: walther@technowledgy.de Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded Content-Language: en-US To: Tom Lane , Thomas Munro Cc: Peter Eisentraut , Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs , Bruce Momjian References: <3561573.1710771812@sss.pgh.pa.us> <4093813.1710899588@sss.pgh.pa.us> <4095435.1710900216@sss.pgh.pa.us> <477fa513-6bf0-456d-8d24-1e22a19df671@technowledgy.de> <36690fcf-f0c8-4d60-af49-6a7efa0e2b14@technowledgy.de> <782438.1711062167@sss.pgh.pa.us> In-Reply-To: <782438.1711062167@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: - List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tom Lane: > Thomas Munro writes: >> Just a thought: if we want to go this way, do we need a new exec call? >> We already control the initial exec in pg_ctl.c. > > I'm resistant to assuming the postmaster is launched through pg_ctl. > systemd, for example, might well prefer not to do that, not to > mention all the troglodytes still using 1990s launch scripts. Right, the systemd example in the docs is not using pg_ctl. But, it should be easily possible to have: - pg_ctl call postgres with a padded argv0 - postgres call itself with padding, if it wasn't called with that already This way, there would be no additional exec call when started through pg_ctl, but one more call when started directly. Best, Wolfgang