Re: BUG #18893: Segfault during analyze pg_database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robins Tharakan <tharakan(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18893: Segfault during analyze pg_database
Date: 2025-04-13 14:13:31
Message-ID: 829593.1744553611@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Robins Tharakan <tharakan(at)gmail(dot)com> writes:
> On Sat, 12 Apr 2025 at 13:05, PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2025-04-13 23:26:10 Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
Previous Message Tom Lane 2025-04-13 14:05:05 Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.