Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
| От | Stefan Heine |
|---|---|
| Тема | Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 |
| Дата | |
| Msg-id | e35fafdb-9b2c-4259-aae5-0e8312a2a8f6@heine7.de обсуждение исходный текст |
| Ответ на | Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 (Thomas Munro <thomas.munro@gmail.com>) |
| Ответы |
Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
|
| Список | 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@postgresql.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?
В списке pgsql-bugs по дате отправления: