| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ubsan |
| Date: | 2022-03-23 19:22:41 |
| Message-ID: | 20220323192241.tzeo6cu6mvepok53@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-23 11:21:37 -0700, Andres Freund wrote:
> On 2022-03-23 13:54:50 -0400, Tom Lane wrote:
> > Andres Freund <andres(at)anarazel(dot)de> writes:
> > > I tried to run postgres with ubsan to debug something.
> >
> > For 0001, could we just replace configure's dlopen check with the
> > dlsym check? Or are you afraid of reverse-case failures?
>
> Yea, I was worried about that. But now that I think more about it, it's hard
> to believe something could provide / intercept dlsym but not dlopen. I guess
> we can try and see?
>
> > 0003: OK. Interesting though that we haven't seen these before.
I think we should backpatch both, based on the reasoning in
46ab07ffda9d6c8e63360ded2d4568aa160a7700 ?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2022-03-23 19:37:02 | Re: Parameter for planner estimate of recursive queries |
| Previous Message | Tom Lane | 2022-03-23 19:02:23 | Re: warn if GUC set to an invalid shared library |