pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shinoda@hpe.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Subject: RE: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
Date: Wed, 2 Dec 2020 01:11:07 +0000
Message-ID: <TU4PR8401MB1152852F826CD699880B6F41EEF30@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1526097.1606856323@sss.pgh.pa.us>
References: <16754-4a800d382f5cfae9@postgresql.org>
	<1526097.1606856323@sss.pgh.pa.us>

> 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.

Thank you for your comment and test.
I tried again with an older version of LLVM below.

- PostgreSQL 13.1
- Red Hat Enterprise Linux 7.5
- LLVM 6.0
- cfe 6.0

I couldn't reproduce the problem int the above environment, so maybe it's a problem in my development environment.

Regards,
Noriyoshi Shinoda

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Wednesday, December 2, 2020 5:59 AM
To: Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shinoda@hpe.com>
Cc: pgsql-bugs@lists.postgresql.org; Andres Freund <andres@anarazel.de>
Subject: Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.

PG Bug reporting form <noreply@postgresql.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





view thread (8+ messages)  latest in thread

Message-ID: <TU4PR8401MB1152852F826CD699880B6F41EEF30@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM>
Permalink:  ../TU4PR8401MB1152852F826CD699880B6F41EEF30@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM/
Also on:    postgresql.org/message-id/TU4PR8401MB1152852F826CD699880B6F41EEF30@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: noriyoshi.shinoda@hpe.com, tgl@sss.pgh.pa.us, andres@anarazel.de
  Subject: Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
  In-Reply-To: <TU4PR8401MB1152852F826CD699880B6F41EEF30@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM>
  References: <16754-4a800d382f5cfae9@postgresql.org> <1526097.1606856323@sss.pgh.pa.us> <TU4PR8401MB1152852F826CD699880B6F41EEF30@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox