This is a VM based on IBM hardware.
I can dig into the HW side if needed.
I will check on jit setting and see if the issue can be resolved.
As for the stack trace, there is no coredump and the search i did, look ile the pg_backtrace may be the way to go. I
havedownloaded the sourxe code from GitHub but looking for the make command options for rhel8.9 and any dependencies.
Regards
Sent from my iPhone
> On Sep 4, 2024, at 4:10 PM, Thomas Munro <thomas.munro@gmail.com> wrote:
>
> On Wed, Sep 4, 2024 at 5:05 PM David Rowley <dgrowleyml@gmail.com> wrote:
>> Ideally, if you could use that to get a stack trace include that here.
>> Alternatively, an even better option would be a self-contained series
>> of SQL statements that we can run and recreate the issue.
>
> If this is an ARM CPU (like AWS Graviton), and if setting "jit=off"
> fixes it, then it could be the known LLVM relocation issue[1], for
> which we have a candidate solution pending. I mention this wild guess
> because we're seeing a lot of these reports and it'd be much easier to
> check that than figure out stack traces etc.
>
> [1]
https://www.postgresql.org/message-id/flat/CAO6_Xqr63qj%3DSx7HY6ZiiQ6R_JbX%2B-p6sTPwDYwTWZjUmjsYBg%40mail.gmail.com
