From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Date: | 2024-03-21 23:23:45 |
Message-ID: | CAD5tBc+JP6a7fe1m8eQDZgzSpntR_bjuFzoXw43yetk4-fXcnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Thu, Mar 21, 2024 at 7:02 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > Just a thought: if we want to go this way, do we need a new exec call?
> > We already control the initial exec in pg_ctl.c.
>
> I'm resistant to assuming the postmaster is launched through pg_ctl.
> systemd, for example, might well prefer not to do that, not to
> mention all the troglodytes still using 1990s launch scripts.
>
> A question that seems worth debating in this thread is how much
> updating the process title is even worth nowadays. It feels like
> a hangover from before we had pg_stat_activity and other monitoring
> support. So I don't feel a huge need to support it on musl.
> 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.
>
>
>
+1
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-03-21 23:30:52 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Previous Message | Thomas Munro | 2024-03-21 23:20:11 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-03-21 23:30:52 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Previous Message | Peter Geoghegan | 2024-03-21 23:21:53 | Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan |