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

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Wolfgang Walther <walther(at)technowledgy(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Date: 2024-03-20 18:37:08
Message-ID: 4d3e5b19-ea58-456d-8074-4f50a6e0a3bd@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 20.03.24 15:37, Wolfgang Walther wrote:
>> It is hard to imagine why we would add an extra exec on every Linux
>> server start for this.
>
> Would this be a problem? For a running server this would happen only
> once when the postmaster starts up, AFAICT.

I wonder if it would cause issues with systemd or similar, if the PID of
the running process is not the one that systemd started. If so, there
is probably a workaround, but it would have to be analyzed.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wolfgang Walther 2024-03-20 19:10:01 Re: Regression tests fail with musl libc because libpq.so can't be loaded
Previous Message Alexander Korotkov 2024-03-20 17:00:32 Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-03-20 18:51:46 Re: REVOKE FROM warning on grantor
Previous Message Nathan Bossart 2024-03-20 18:35:27 Re: cleanup patches for incremental backup