Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Emmanuel Sibi <emmanuelsibi.mec@gmail.com>,
pgsql-hackers@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Date: 2025-11-05T16:05:00Z
Lists: pgsql-hackers
Jacob Champion <jacob.champion@enterprisedb.com> writes: > On Tue, Nov 4, 2025 at 5:19 PM Tom Lane <tgl@sss.pgh.pa.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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid possible crash within libsanitizer.
- d4baa327a1c9 19 (unreleased) landed
- c775bf048abd 16.11 landed
- a9515f294de1 17.7 landed
- 6d8acb777715 18.1 landed