Re: PostgreSQL 17 Segmentation Fault

From: Cameron Vogt <cvogt(at)automaticcontrols(dot)net>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(at)vondra(dot)me>, Michael Paquier <michael(at)paquier(dot)xyz>, Sean Massey <sean(dot)f(dot)massey(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL 17 Segmentation Fault
Date: 2024-10-05 22:11:54
Message-ID: DM6PR16MB3145A4E93F2E016D4154F069AB732@DM6PR16MB3145.namprd16.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2024-10-05 01:40:17 Thomas Munro
<thomas(dot)munro(at)gmail(dot)com> wrote:
> Could it be an instance of LLVM's ARM relocation bug?

After reading about the bug, I believe you are likely correct. That would explain the behavior I'm seeing with JIT and shared_buffers. When I migrated PostgreSQL versions, I also moved to a new aarch64 machine. The old machine was not aarch64, so that may explain the timing of the issue as well.

Cameron Vogt | Software Developer
Direct: 314-756-2302 | Cell: 636-388-2050
1585 Fencorp Drive | Fenton, MO 63026
Automatic Controls Equipment Systems, Inc.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andy Fan 2024-10-06 04:19:46 Re: what are the things that occupy the session memory.
Previous Message Tom Lane 2024-10-05 18:48:05 Re: BUG #18637: CREATE INDEX won't look up operator classes in search_path if PARTITION BY is specified