From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | walther(at)technowledgy(dot)de, Peter Eisentraut <peter(at)eisentraut(dot)org>, Christophe Pettus <xof(at)thebuild(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Date: | 2024-03-21 23:20:11 |
Message-ID: | CA+hUKGL8X8bv9C11sW8g6Zn3TTLmaKNJMa5Nb57o5jsz6rr7sQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Fri, Mar 22, 2024 at 12:02 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2024-03-21 23:23:45 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Previous Message | Tom Lane | 2024-03-21 23:02:47 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2024-03-21 23:21:53 | Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan |
Previous Message | Tom Lane | 2024-03-21 23:17:28 | Re: Catalog domain not-null constraints |