Re: Cancelling parallel query leads to segfault

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Cancelling parallel query leads to segfault
Date: 2018-02-06 17:06:09
Message-ID: 20180206170609.pypo43tdv3oyv5kp@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-02-06 18:33:45 Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Previous Message Peter Eisentraut 2018-02-06 17:01:08 Re: Cancelling parallel query leads to segfault