Re: Cancelling parallel query leads to segfault

Поиск
Список
Период
Сортировка
Искать
От
Andres Freund
Тема
Re: Cancelling parallel query leads to segfault
Дата
Msg-id
20180206170609.pypo43tdv3oyv5kp@alap3.anarazel.de
Ответ на
Список
Дерево обсуждения
Cancelling parallel query leads to segfault Andres Freund <andres@anarazel.de>
Re: Cancelling parallel query leads to segfault Robert Haas <robertmhaas@gmail.com>
Re: Cancelling parallel query leads to segfault Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Cancelling parallel query leads to segfault Andres Freund <andres@anarazel.de>
Re: Cancelling parallel query leads to segfault Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Cancelling parallel query leads to segfault Andres Freund <andres@anarazel.de>
Re: Cancelling parallel query leads to segfault Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Cancelling parallel query leads to segfault Andres Freund <andres@anarazel.de>
Re: Cancelling parallel query leads to segfault Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
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
> >  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 по дате отправления
От: Peter Eisentraut
Дата:
От: Peter Geoghegan
Дата:
FAQ