From: | walther(at)technowledgy(dot)de |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | 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-22 08:12:47 |
Message-ID: | c72625ba-0a3d-4cd7-ad85-b467b44454ec@technowledgy.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Tom Lane:
> 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.
Right, the systemd example in the docs is not using pg_ctl.
But, it should be easily possible to have:
- pg_ctl call postgres with a padded argv0
- postgres call itself with padding, if it wasn't called with that already
This way, there would be no additional exec call when started through
pg_ctl, but one more call when started directly.
Best,
Wolfgang
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2024-03-22 08:28:29 | Re: Index plan returns different results to sequential scan |
Previous Message | Wolfgang Walther | 2024-03-22 08:02:04 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
From | Date | Subject | |
---|---|---|---|
Next Message | Anton A. Melnikov | 2024-03-22 08:14:48 | Re: Bug in nbtree optimization to skip > operator comparisons (or < comparisons in backwards scans) |
Previous Message | Pavel Borisov | 2024-03-22 08:02:49 | Re: Bug in nbtree optimization to skip > operator comparisons (or < comparisons in backwards scans) |