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

From: Quan Zongliang <quanzongliang(at)yeah(dot)net>
To: Emmanuel Sibi <emmanuelsibi(dot)mec(at)gmail(dot)com>
Cc: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization
Date: 2025-09-23 03:08:47
Message-ID: a3011d7c-4363-4c27-8f7b-3999cfee7a1f@yeah.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/15/25 11:19 PM, Emmanuel Sibi wrote:
> Hi Quan, Thanks for testing the patch! I'm glad it resolves the startup crash.
>
> Fast shutdown:
> 2025-09-15 20:20:07.454 IST [28229] LOG: received fast shutdown request
> [...]
> 2025-09-15 20:20:07.574 IST [28229] LOG: database system is shut down
> Smart shutdown:
> 2025-09-15 20:28:14.271 IST [31263] LOG: received smart shutdown request
> [...]
> 2025-09-15 20:28:14.399 IST [31263] LOG: database system is shut down
>
> All modes complete within seconds with the final "database system is
> shut down" message, unlike the hang you're experiencing.
> The patch only moves __ubsan_default_options() to a separate
> compilation unit to avoid TSan initialization issues during startup.
> It doesn't modify any shutdown logic or signal handling code.
> My Environment: Ubuntu 24.04.1, clang 18, PostgreSQL 17.2.
>
Great! My OS is macOS 15.6.1. I will continue to test to confirm if
there are any other issues. If so, I will create a separate patch.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Чумак Антон 2025-09-23 03:38:31 Re: [PATCH] Introduce unified support for composite GUC options
Previous Message Rintaro Ikeda 2025-09-23 02:58:29 Re: Suggestion to add --continue-client-on-abort option to pgbench