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 1rn1KD-00BCOk-QY for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Mar 2024 19:10:10 +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 1rn1KC-007TvJ-0I for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Mar 2024 19:10:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rn1KB-007TvB-OT for pgsql-bugs@lists.postgresql.org; Wed, 20 Mar 2024 19:10:08 +0000 Received: from dd25110.kasserver.com ([85.13.146.49]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rn1K8-005XkP-AX for pgsql-bugs@lists.postgresql.org; Wed, 20 Mar 2024 19:10:07 +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 E97F2E1A012C; Wed, 20 Mar 2024 20:10:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technowledgy.de; s=kas202308201259; t=1710961802; bh=pX5gM7Bx+Rebibf/rK9hgb+MeeyxD5xw41QIRUV694k=; h=Date:From:Subject:To:Cc:References:In-Reply-To:From; b=A3ZPbtartptPuhpbPQVcUwxTZycou6geR3gT5UEA02Ubl1OH+E9LAMEx2g0YETCCS Vrxkv88S1592+vFvdd7N8LNGCnsDxMKkzyonnYZa5WnwVcVtaA2brN+VGZgoaFlt38 j9Unwo2pTiUwtAOvZ2vvY9iGhoiRfAPDFvbdfbL2BADA49+cTzILEckCwVVd5H5vli FYCtvq0y3mwJkGIMZQh22E2cu8SQQRePOq04Ew/7n6IltH7uLqc963TgtKnxi1BrtB eHXbQWooBhKHqyCLBcILw5H70Qu+1eXYFaQLc5t1fQ6g+apy1WOcNyTvzSNQEOac55 cHei5ztQZ9xMw== Message-ID: <721bedec-35e7-453d-a442-aeba9fb01399@technowledgy.de> Date: Wed, 20 Mar 2024 20:10:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Wolfgang Walther Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded Content-Language: en-US To: Peter Eisentraut , Bruce Momjian Cc: Thomas Munro , Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs , Tom Lane 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> <4d3e5b19-ea58-456d-8074-4f50a6e0a3bd@eisentraut.org> In-Reply-To: <4d3e5b19-ea58-456d-8074-4f50a6e0a3bd@eisentraut.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: / List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut: >> Would this be a problem? For a running server this would happen only >> once when the postmaster starts up, AFAICT. > > I wonder if it would cause issues with systemd or similar, if the PID of > the running process is not the one that systemd started.  If so, there > is probably a workaround, but it would have to be analyzed. I don't think that exec even creates a new PID. The current process is replaced, so the PID stays the same. Best, Wolfgang