Re: Regression tests fail with musl libc because libpq.so can't be loaded - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Regression tests fail with musl libc because libpq.so can't be loaded
Date
Msg-id ZgH8GiD0CqYrTPQq@momjian.us
Whole thread Raw
In response to Re: Regression tests fail with musl libc because libpq.so can't be loaded  (walther@technowledgy.de)
Responses Re: Regression tests fail with musl libc because libpq.so can't be loaded  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Regression tests fail with musl libc because libpq.so can't be loaded  (walther@technowledgy.de)
List pgsql-bugs
On Mon, Mar 25, 2024 at 10:58:30PM +0100, walther@technowledgy.de wrote:
> Bruce Momjian:
> > With no one "hoping this patch dies in a fire"*, I have updated it with
> > more details, which I now think is committable to master.  Is this
> > something to backpatch?  Seems too rare a bug to me.
> 
> I would like to see this backpatched to be able to run the regression tests
> easily on all stable branches.

You want to risk destabilizing Postgres by backpatching something this
complex so the regression tests can be run on all stable branches?  I
think you are overestimating our desire to take on risk.

Also, in my patch, the parentheses here:

    #if defined(__linux__) && (! defined(__GLIBC__) && ! defined(__UCLIBC__))

are unnecessary so they should be removed:

    #if defined(__linux__) && ! defined(__GLIBC__) && ! defined(__UCLIBC__)

I am only willing to apply my patch, and only to master.  Other
committers might be more willing.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



pgsql-bugs by date:

Previous
From: walther@technowledgy.de
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Next
From: Peter Eisentraut
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded