Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization
Emmanuel Sibi <emmanuelsibi.mec@gmail.com>
From: Emmanuel Sibi <emmanuelsibi.mec@gmail.com>
To: Aleksander Alekseev <aleksander@tigerdata.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-09-08T16:43:54Z
Lists: pgsql-hackers
Hi Aleksander, > Thanks for reporting this. Did you investigate whether Meson also has > this issue? Fixing anything for Autotools arguably has low priority > since we are going to get rid of it in the near future, but Meson is > another matter. Thanks for the reply. Yes, I tested with Meson and confirmed the same issue occurs. When building PostgreSQL 17.2 with ThreadSanitizer: meson setup builddir \ --prefix=/path/to/install \ --buildtype=debug \ -Dcassert=true \ -Dtap_tests=enabled \ -Db_lto=false \ -Db_sanitize=thread \ -Db_lundef=false \ -Dc_args="-O0 -g -gdwarf-2 -fno-omit-frame-pointer" The postgres binary segfaults during early initialization, exactly as with the Autotools build. Applying the patch I submitted, which moves __ubsan_default_options() to a separate compilation unit built without sanitizer instrumentation, successfully resolves the segfault. Thanks & regards, Emmanuel Sibi
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