Re: BUG #15290: Stuck Parallel Index Scan query - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #15290: Stuck Parallel Index Scan query
Date
Msg-id 20180723043544.xg2yvsj6r6b2yuhb@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #15290: Stuck Parallel Index Scan query  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-bugs
On 2018-07-23 16:30:28 +1200, Thomas Munro wrote:
> TerminateBackgroundWorker() sets a shm flag and signals the
> postmaster, the postmaster signals the worker with SIGTERM, the worker
> handles SIGTERM in die() by setting ProcDiePending = true,
> InterruptPending= true and then setting its own latch, and the
> ConditionVarableSleep() loop should wake up, go around its loop again
> and run CHECK_FOR_INTERRUPTS() which sees InterruptPending and runs
> ProcessInterrupts(), which sees ProcDiePending and reports FATAL.  So
> which domino fell short here?

I've not looked at this, but is it possible that interrupts aren't
accepted because they're held (e.g. because of an lwlock)?

Greetings,

Andres Freund


pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #15290: Stuck Parallel Index Scan query
Next
From: Victor Yegorov
Date:
Subject: Re: BUG #15290: Stuck Parallel Index Scan query