Re: Regression tests fail with musl libc because libpq.so can't be loaded

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: walther(at)technowledgy(dot)de, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Date: 2024-03-25 23:14:25
Message-ID: 2712255.1711408465@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Mon, Mar 25, 2024 at 10:58:30PM +0100, walther(at)technowledgy(dot)de wrote:
>> 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.

If we want a buildfarm animal testing this platform, we kind of need
to support it on all branches. Having said that, I agree with you
that we are looking for a minimalist fix not a maximalist one.
I think the 0001 patch is about right, but the rest seem to be solving
problems we don't have.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-03-25 23:15:52 Re: Regression tests fail with musl libc because libpq.so can't be loaded
Previous Message Thomas Munro 2024-03-25 22:54:59 Re: Regression tests fail with musl libc because libpq.so can't be loaded

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-03-25 23:15:52 Re: Regression tests fail with musl libc because libpq.so can't be loaded
Previous Message Andrew Dunstan 2024-03-25 23:14:18 Re: session username in default psql prompt?