From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: walther@technowledgy.de, Peter Eisentraut <peter@eisentraut.org>,
        Christophe Pettus <xof@thebuild.com>,
        Andrew Dunstan <andrew@dunslane.net>,
        PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>,
        Bruce Momjian <bruce@momjian.us>
Subject: Re: Regression tests fail with musl libc because libpq.so can't be
 loaded
In-reply-to: 
 <CA+hUKGL8X8bv9C11sW8g6Zn3TTLmaKNJMa5Nb57o5jsz6rr7sQ@mail.gmail.com>
References: <3561573.1710771812@sss.pgh.pa.us>
 <CA+hUKG+Tq3GK7bPd03N0Eox3YY4-Hjd7qQjo_QZFjdbhTqQGQA@mail.gmail.com>
 <CA+hUKGK9LUq=uygBRFt3vFO1RL+_scsT4+hMkvea_zTttHZ59Q@mail.gmail.com>
 <ZfolyUQw9z1zxX58@momjian.us>
 <CA+hUKG+Y1D2Bv9v0GbYrhiQ+mhf=6Xj2_viiATnBVFShkfO4VQ@mail.gmail.com>
 <4093813.1710899588@sss.pgh.pa.us>
 <CA+hUKGKNK5V8XwwJJZm36s3EUy8V51xu4XiE8=26n=Wq3OGd4A@mail.gmail.com>
 <4095435.1710900216@sss.pgh.pa.us>
 <CA+hUKGK2cSx3dveMqBD+E9N=zJ0WawBcbk_jnPqmdWBM0DT_3Q@mail.gmail.com>
 <477fa513-6bf0-456d-8d24-1e22a19df671@technowledgy.de>
 <ZfrmN4WHuJgD95fw@momjian.us>
 <CA+hUKGJzC4rr2Yr=QZyx9W83Wv=TVJHndKF1anjNLNXVUM7TqQ@mail.gmail.com>
 <f98cd8de-1c66-491a-8409-e62c09932080@technowledgy.de>
 <36690fcf-f0c8-4d60-af49-6a7efa0e2b14@technowledgy.de>
 <CA+hUKGJAkTZUa9JGr-zsadaqsN=K0P71t-1L2t2=MQFDMc4GuQ@mail.gmail.com>
 <782438.1711062167@sss.pgh.pa.us>
 <CA+hUKGL8X8bv9C11sW8g6Zn3TTLmaKNJMa5Nb57o5jsz6rr7sQ@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Fri, 22 Mar 2024 12:20:11 +1300"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <795675.1711063852.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Thu, 21 Mar 2024 19:30:52 -0400
Message-ID: <795676.1711063852@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/795676.1711063852%40sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.com> writes:
> On Fri, Mar 22, 2024 at 12:02 PM Tom Lane <tgl@sss.pgh.pa.us> 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.

No real objection here.  I do wonder about the point you (or somebody)
made upthread that we don't have any testing of the PS_USE_NONE case;
but that could be addressed some other way.

			regards, tom lane