| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Wolfgang Walther <walther(at)technowledgy(dot)de>, 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-18 14:23:32 |
| Message-ID: | 3561573.1710771812@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> (Hmm, I think it's not that unreasonable on their part to assume the
> initial environment is immutable if their implementation doesn't
> mutate it, and our doing so is undeniably UB; surprising, maybe, given
> that the technique works on that other popular brand of C library on
> that kind of kernel, not to mention dozens of old Unixen of yore...
Does their implementation also ignore the effects of putenv() or
setenv() on LD_LIBRARY_PATH? They have no moral high ground
whatsoever if that's the case. But if it doesn't, an alternative
route to a solution could be to scan the original environment, strdup
and putenv each entry to move it to freshly malloc'd space, and
then reclaim the old environment area.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2024-03-18 20:18:08 | Re: Postgres jdbc driver inconsistent behaviour with double precession |
| Previous Message | PG Bug reporting form | 2024-03-18 14:05:58 | BUG #18398: Simplified SQL Query for Problem Diagnosis |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2024-03-18 14:29:21 | Re: Improving EXPLAIN's display of SubPlan nodes |
| Previous Message | Michał Kłeczek | 2024-03-18 14:17:54 | Re: DRAFT: Pass sk_attno to consistent function |