| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | kchaid(at)hotmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18599: server closed the connection unexpectedly |
| Date: | 2024-09-04 21:09:16 |
| Message-ID: | CA+hUKGKPK46eoPD+hCyDFjZFNP72eu5Pvpa2Jc3qUk-nenvHaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Sep 4, 2024 at 5:05 PM David Rowley <dgrowleyml(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haifang Wang (Centific Technologies Inc) | 2024-09-04 21:28:22 | RE: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607 |
| Previous Message | Francois Jourdain | 2024-09-04 16:57:25 | Re: bug when using special caracter in password for folder. |