| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Cancelling parallel query leads to segfault |
| Date: | 2018-02-06 17:01:08 |
| Message-ID: | 97146730-fc27-14ea-d15a-a322ed8cfb5c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-02-06 17:06:09 | Re: Cancelling parallel query leads to segfault |
| Previous Message | Robert Haas | 2018-02-06 16:36:50 | Re: [HACKERS] path toward faster partition pruning |