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
In-reply-to: 
 <CAEP4nAzFvFfj5kfJcBLQ1HVQwuydABCD2=rzPbM7Fn2WiEptGQ@mail.gmail.com>
References: <18893-da17531047e6447f@postgresql.org>
 <CAEP4nAzFvFfj5kfJcBLQ1HVQwuydABCD2=rzPbM7Fn2WiEptGQ@mail.gmail.com>
Comments: In-reply-to Robins Tharakan <tharakan@gmail.com>
	message dated "Sun, 13 Apr 2025 21:41:00 +0930"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <829592.1744553611.1@sss.pgh.pa.us>
Date: Sun, 13 Apr 2025 10:13:31 -0400
Message-ID: <829593.1744553611@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/829593.1744553611%40sss.pgh.pa.us>
Precedence: bulk

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