Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call' - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
Date
Msg-id CA+hUKGKxuj3JzEa3X_UOF8QGVtFUEOgLiMHJHLfkNdz3mEwi0w@mail.gmail.com
Whole thread Raw
In response to BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
List pgsql-bugs
Tree view 
On Mon, Jun 29, 2020 at 9:19 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      16516
> Logged by:          reiner peterke
> Email address:      reiner.peterke@splendiddata.com
> PostgreSQL version: 12.3
> Operating system:   Centos 7.8.2003, redhat 7.8, sles 12 sp5
> Description:
>
> Testing jit functionality power8 architecture

> terminate called after throwing an instance of 'std::bad_function_call'

Hi, I think this was a problem with LLVM on POWER with LLVM versions
before 7.  There have been a couple of discussions of it in the mail
archives, and the problem was on the LLVM side, fixed in later
releases.  I suspect you either need to somehow get a build with newer
LLVM, or you need to disable jit.

pgsql-bugs by date:

Previous
From: Hamid Akhtar
Date:
Subject: Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: [BUG][PATCH] ecpg crash with bytea type and cursors