Re: seawasp failing, maybe in glibc allocator - Mailing list pgsql-hackers

From Andres Freund
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id 20210620110107.e4wvqr5vtirxfo2g@alap3.anarazel.de
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: seawasp failing, maybe in glibc allocator  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Hi,

On 2021-06-19 10:12:03 -0400, Tom Lane wrote:
> Is a compile-time conditional really going to be reliable?  See nearby
> arguments about compile-time vs run-time checks for libpq features.
> It's not clear to me how tightly LLVM binds its headers and running
> code.

It should be fine (and if not we have plenty other places it'd be
problematic). LLVM embeds the version between user of llvm and the
library version in some symbol, so if there's a sufficient mismatch
it'll cause link time issues. Of course that only works for major
versions, but that shouldn't be an issue here.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: seawasp failing, maybe in glibc allocator
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: locking [user] catalog tables vs 2pc vs logical rep