Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: noriyoshi(dot)shinoda(at)hpe(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
Date: 2020-12-01 20:58:43
Message-ID: 1526097.1606856323@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> SELECT pg_cancel_backend(130342);
> ...
> 2020-12-01 14:26:02.337 JST [130270] LOG: background worker "parallel
> worker" (PID 130342) was terminated by signal 11: Segmentation fault
> 2020-12-01 14:26:02.337 JST [130270] DETAIL: Failed process was running:
> EXPLAIN ANALYZE SELECT * FROM data1 d1, data1 d2;

FWIW, I failed to reproduce any crash here, using RHEL8 (llvm-10.0.1).
I don't see any plausibly-related commits since 13.1, so it's not
something we recently fixed. I wonder if this is an LLVM bug fixed
since the 7.1 release you have.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Shinoda, Noriyoshi (PN Japan FSIP) 2020-12-02 01:11:07 RE: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
Previous Message Tom Lane 2020-12-01 17:07:41 Re: BUG #16758: create temporary table with the same name loses defaults, indexes