| From: | Stefan Heine <github(dot)stheine(at)heine7(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 |
| Date: | 2024-06-12 13:47:44 |
| Message-ID: | e35fafdb-9b2c-4259-aae5-0e8312a2a8f6@heine7.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2024-06-12 02:59, Thomas Munro wrote:
> On Tue, Jun 11, 2024 at 10:08 PM PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>> The query described in
>> https://www.postgresql.org/message-id/flat/18471-4e01d7601cedf1b0%40postgresql.org
>> is causing a reproducible 'Segmentation fault'.
> Also on ARM?
yes, this is ARM (aarch64).
> 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?
when jit is disabled, the query runs ok in < 2 seconds.
when the issue happens, it takes > 30 seconds and then results in a 6GB
core.
>> 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?
find a core here:
https://my.hidrive.com/share/bz2zb2alkp
do you have instructions for the gdb backtrace?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2024-06-12 13:51:30 | BUG #18506: Memory Leak on wrong INNER JOINs |
| Previous Message | Francisco Olarte | 2024-06-12 11:56:02 | Re: Issue Report: Unique Constraint Violation Error in PostgreSQL |