RE: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend. - Mailing list pgsql-bugs

From Shinoda, Noriyoshi (PN Japan FSIP)
Subject RE: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
Date
Msg-id TU4PR8401MB1152129A3B9BAF05A34C7F03EECE0@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
List pgsql-bugs
Hi,

Thanks for the comment.
I newly cloned the latest version 13.1 source and then rebuilt it. The segmentation fault has recurred.I tried the
backtracefeature, but it didn't work. The function specification may not have been good. 
Segmentation faults do not always occur, but occasionally after running pg_cancel_backend several times.
Also, it only seems to happen if I canceled the parallel worker process.

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

Hi,

On 2020-12-02 01:11:07 +0000, Shinoda, Noriyoshi (PN Japan FSIP) wrote:
> > I don't see any plausibly-related commits since 13.1, so it's not something we recently fixed.  I wonder if this is
anLLVM 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

Could you try to reproduce the issue with the version you hit it earlier? It'd be helpful to get a backtrace.


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

Did you have any modifications in the tree?

Did you do a build, pulled some updates, and built again? I noticed that you didn't pass --enable-depend to
./configure,so it's possible that not all files got rebuilt that needed to. 

Regards,

Andres

Attachment

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16764: wal sender exits abnormally which cause wal receiever exits twice
Next
From: PG Bug reporting form
Date:
Subject: BUG #16765: db1st: while creating EDMX model Npgsql.PostgresException: 42703: column d.adsrc does not exist