Re: Instability of phycodorus in pg_upgrade tests with JIT

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Instability of phycodorus in pg_upgrade tests with JIT
Date: 2026-03-14 07:00:00
Message-ID: 3da9614e-f893-4e29-bb7d-c9f31fee91b2@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Andres,

24.10.2025 17:20, Andres Freund wrote:
>> I wonder if we should just write these off as "probably an LLVM bug".
> I'm not sure that's really convincing, given that REL_16_STABLE seems to not
> have an issue?

FWIW, petalure with llvm 4.0.1 has produced the first crash due to
"double free or corruption (!prev)" in REL_16_STABLE too:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=petalura&dt=2026-03-14%2002%3A03%3A06

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2026-03-14 07:40:03 Re: Row pattern recognition
Previous Message Masahiko Sawada 2026-03-14 04:10:31 Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions