Re: Instability of phycodorus in pg_upgrade tests with JIT - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Instability of phycodorus in pg_upgrade tests with JIT
Date
Msg-id 2b280c41-236d-4cd3-a7e3-ea86d5c1e257@gmail.com
Whole thread Raw
In response to Re: Instability of phycodorus in pg_upgrade tests with JIT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Instability of phycodorus in pg_upgrade tests with JIT
List pgsql-hackers
Hello Tom and Michael,

16.10.2025 02:39, Tom Lane wrote:
Michael Paquier <michael@paquier.xyz> writes:
I have spotted a couple of buildfarm failures for buildfarm member
phycodorus on REL_14_STABLE and REL_13_STABLE:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=phycodurus&dt=2025-10-15%2009%3A12%3A36
phycodorus seems to be running a remarkably ancient LLVM version.
I wonder if we should just write these off as "probably an LLVM bug".

I collected all of such failures here:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures#check-pg_upgrade_fails_on_LLVM-enabled_animals_due_to_double_free_or_corruption

Masao-san was going to dig into that:
https://www.postgresql.org/message-id/CAHGQGwFcjccSYX+Ap8meEbCccUei-B4tmYsBFu4wMEixKi90fQ@mail.gmail.com

Best regards,
Alexander

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Making pg_rewind faster
Next
From: Philip Alger
Date:
Subject: Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement