Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Emmanuel Sibi <emmanuelsibi(dot)mec(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization
Date: 2025-11-05 16:05:00
Message-ID: 834358.1762358700@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> On Tue, Nov 4, 2025 at 5:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Assuming that works for Emmanuel, we could wrap it in a
>> pg_disable_sanitizer_instrumentation macro, or just use it
>> as-is. I don't have a strong preference --- any thoughts?

> No preference on my end. (If a second place to use it pops up, we
> could wrap it then.)

Yeah, that's what I concluded after sleeping on it. Right now
it seems unlikely that there will be more usages, so adding a
macro in c.h would just slow down the build (admittedly only
microscopically) for no gain. If we find additional usages
then we can revisit that tradeoff.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Alger 2025-11-05 16:21:48 Re: [PATCH] Add pretty formatting to pg_get_triggerdef
Previous Message Paul A Jungwirth 2025-11-05 16:04:21 Re: SQL:2011 Application Time Update & Delete