Re: Configure with thread sanitizer fails the thread test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Mikhail Matrosov <mikhail(dot)matrosov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, ewan_higgs(at)yahoo(dot)co(dot)uk, robertmhaas(at)gmail(dot)com
Subject: Re: Configure with thread sanitizer fails the thread test
Date: 2021-07-23 21:18:37
Message-ID: 997998.1627075117@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-07-23 13:42:41 -0400, Tom Lane wrote:
>> TBH, I wonder why we don't just nuke thread_test.c altogether.

> +1. And before long it might be time to remove support for systems
> without threads...

I'm not prepared to go that far just yet; but certainly we can stop
expending configure cycles on the case.

Should we back-patch this, or just do it in HEAD? Maybe HEAD+v14?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2021-07-23 21:24:04 Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)
Previous Message Tom Lane 2021-07-23 21:15:24 Removing "long int"-related limit on hash table sizes