From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robins Tharakan <tharakan@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18893: Segfault during analyze pg_database
Date: Sun, 13 Apr 2025 10:13:31 -0400
Message-ID: <829593.1744553611@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEP4nAzFvFfj5kfJcBLQ1HVQwuydABCD2=rzPbM7Fn2WiEptGQ@mail.gmail.com>
References: <18893-da17531047e6447f@postgresql.org>
<CAEP4nAzFvFfj5kfJcBLQ1HVQwuydABCD2=rzPbM7Fn2WiEptGQ@mail.gmail.com>
Robins Tharakan <tharakan@gmail.com> writes:
> On Sat, 12 Apr 2025 at 13:05, PG Bug reporting form <noreply@postgresql.org>
> wrote:
>> Creating a few Databases followed by CHECKPOINT causes a segfault.
> Simply running pgbench (or any workload that triggers AV) causes a segfault.
At this point I'm starting to suspect a compiler bug (or hardware fault?)
on your machine. I spent awhile last night trying to replicate your
previous report and failed, both on x86_64/RHEL8 and Apple M4/Sequoia.
Moreover, we're not seeing the sort of instability in the buildfarm
that would inevitably appear if AV were as broken as it seems to be
for you.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tharakan@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18893: Segfault during analyze pg_database
In-Reply-To: <829593.1744553611@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox