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 1rnSSy-00DNhI-G6 for pgsql-bugs@arkaria.postgresql.org; Fri, 22 Mar 2024 00:09:00 +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 1rnSSw-00HELl-Oo for pgsql-bugs@arkaria.postgresql.org; Fri, 22 Mar 2024 00:08:59 +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 1rnSSw-00HELd-Gq for pgsql-bugs@lists.postgresql.org; Fri, 22 Mar 2024 00:08:59 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rnSSo-005kzD-UO for pgsql-bugs@lists.postgresql.org; Fri, 22 Mar 2024 00:08:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=ruerbVGs/XfsrK8vEmau2FgnJanRr03tSEzJ/KNcivg=; b=jj++lZuMv/8p+HpJTOEgWujuAP jBESQUMNhMyHB7i8cT+IWH0VHHotdpXew5OXNbCa/Y4OhJJ39tUGTQz6Apb98PYKbH8xo4oqbZFID B7GVlWnfhMZPugX2vfUkDGKtP9KVhrx7FezLivSs9VDBjaqGonkBXdRQ5ooP6ENc7aMQGHPdB/C0g tvYAPfBX2YeauBJ74YQv8OK3nL1Fbbjpg7r2+UsQkGXrDi1Hz9xUJujX9w3OCi6JXfd4TzQJRSCDq 1mQMia24DAQOpsSdFH83wweUC3Kj7lc/+SEAwjlwlGxshvnORgsqwsZvgF6w/LhqxL6OKLNJOcy3W 4TEQWK/A==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1rnSSn-004FoP-0W; Thu, 21 Mar 2024 20:08:49 -0400 Date: Thu, 21 Mar 2024 20:08:49 -0400 From: Bruce Momjian To: Thomas Munro Cc: Tom Lane , walther@technowledgy.de, Peter Eisentraut , Christophe Pettus , Andrew Dunstan , PostgreSQL Bugs Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded Message-ID: References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Mar 22, 2024 at 12:20:11PM +1300, Thomas Munro wrote: > On Fri, Mar 22, 2024 at 12:02 PM Tom Lane wrote: > > The previously-suggested patch to whitelist glibc and variants, > > and otherwise fall back to PS_USE_NONE, seems like it might be > > the appropriate amount of effort. > > What about meeting musl halfway: clobber argv, but only clobber > environ for the libcs known to tolerate that? Then musl might see > truncation at 30-60 characters or whatever it is, but that's probably > enough to see your cluster_name and backend type/user name which is > pretty useful information. I just posted a prototype patch to implement this. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.