Re: Cancelling parallel query leads to segfault - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Cancelling parallel query leads to segfault
Date
Msg-id 20180206170609.pypo43tdv3oyv5kp@alap3.anarazel.de
Whole thread Raw
In response to Re: Cancelling parallel query leads to segfault  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Cancelling parallel query leads to segfault  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2018-02-06 12:01:08 -0500, Peter Eisentraut wrote:
> On 2/1/18 20:35, Andres Freund wrote:
> > On February 1, 2018 11:13:06 PM GMT+01:00, Peter Eisentraut
> > <peter.eisentraut@2ndquadrant.com> wrote:
> >>Here is a patch to implement that idea. Do you have a way to test it
> >>repeatedly, or do you just randomly cancel queries?
> > 
> > For me cancelling the long running parallel queries I tried reliably
> > triggers the issue. I encountered it while cancelling tpch q1 during JIT
> > work.
> 
> Why does canceling a query result in elog(FATAL)?  It should just be
> elog(ERROR), which wouldn't trigger this issue.

The workers are shut down.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Cancelling parallel query leads to segfault
Next
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)