Re: BUG #18599: server closed the connection unexpectedly

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