From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Ewan Higgs <ewan_higgs(at)yahoo(dot)co(dot)uk>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Configure with thread sanitizer fails the thread test |
Date: | 2015-08-18 15:14:26 |
Message-ID: | CA+Tgmoage-ttrJn3R4AksxQU9pXAG8xm3EiLvVjkuhgrr32xQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 17, 2015 at 3:02 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-08-17 14:31:24 -0300, Alvaro Herrera wrote:
>> The postmaster process in particular runs in a rather unusual
>> arrangement, where most of the interesting stuff does happen in signal
>> handlers.
>
> FWIW, I think it might be worthwhile to convert postmaster into a loop
> over a process local latch, with that latch being set in signal
> handlers. My feeling is that that'd simplify the code rather
> significantly. I'm not 100% it's worth the code churn, but it'd
> definitely be easier to understand. Thread sanitizer isn't the first
> analysis tool that has problems coping with forks in signal handlers
> btw, valgrind on amd64 for a long while had misaligned stacks in the
> children afterwards leading to very odd crashes.
Yeah, I'm a little worried about whether we'd destabilize things by
changing them in that way, but if we could avoid that pitfall I
suspect we'd end up better off.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Charles Sheridan | 2015-08-18 15:41:31 | Colon Omitted From pgSQL Assignments |
Previous Message | Robert Haas | 2015-08-18 15:12:36 | Re: Our trial to TPC-DS but optimizer made unreasonable plan |