Re: BUG #18893: Segfault during analyze pg_database - Mailing list pgsql-bugs

From Robins Tharakan
Subject Re: BUG #18893: Segfault during analyze pg_database
Date
Msg-id CAEP4nAyVgr8nfmud+8KO0=t6pudBLsNOmpz1idNTrOs8zCxzLA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18893: Segfault during analyze pg_database  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs


On Sun, 13 Apr 2025 at 23:43, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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.
 
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.

Thanks for confirming (non-reproducibility).

I didn't see any disk errors / memtest returned nothing / machine uses stock gcc (v12.2.0-14 - Ubuntu bookworm).

I could reproduce this at will until this morning but not any more. A fresh git clone and compile in another folder on the same machine proved that the machine is okay, so my current guess is that I fell victim to not doing a 'git clean -xdf' when I was double-checking (before reporting). In most of my reports I try to triage the commit (which ensures this doesn't happen) - but I had to bypass that step this time since this was not a simple repro.

Apologies for the noise, and once again thanks for taking a look.
-
robins

pgsql-bugs by date:

Previous
From: Gang Chen
Date:
Subject: 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
Next
From: Lele Gaifax
Date:
Subject: Missing whitespace in pg_restore manpage