From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | github(dot)stheine(at)heine7(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 |
Date: | 2024-06-12 00:59:08 |
Message-ID: | CA+hUKGJNtO=wZ2X1nDpFDrF_J7Xo7LnFinaTh-qT2vmqoHSJKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Jun 11, 2024 at 10:08 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> The query described in
> /message-id/flat/18471-4e01d7601cedf1b0%40postgresql.org
> is causing a reproducible 'Segmentation fault'.
Also on ARM?
That other report said that memory is leaking and implies (?) the OOM
killer, but you're talking about a segmentation fault, so it seems
like a different symptom (even if the root cause is same), right?
> That situation is clearly reproducible, so we can help troubleshooting in
> case you want to look into details.
Can you get a core file, and gdb backtrace?
From | Date | Subject | |
---|---|---|---|
Next Message | 王 海 | 2024-06-12 02:11:01 | 回复: BUG #18502: Upsert on view returns 42P10 error when condition is an expression |
Previous Message | Tom Lane | 2024-06-11 20:54:31 | Re: BUG #18502: Upsert on view returns 42P10 error when condition is an expression |