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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services