Horton

Re: Inval reliability, especially for inplace updates

Alexander Lakhin <exclusion@gmail.com>

View thread
From: Alexander Lakhin <exclusion@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>, Nitin Motiani <nitinmotiani@google.com>, Andres Freund <andres@anarazel.de>, Ilyasov Ian <ianilyasov@outlook.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Surya Poondla <s_poondla@apple.com>
Date: 2025-12-17T05:00:00Z
Lists: pgsql-hackers 
Hello Noah,

17.12.2025 05:23, Noah Misch wrote:
> I pushed the patch bundle to v17-v14.  Thanks for the reviews!  The
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dragonet&dt=2025-12-17%2001%3A34%3A36
> "double free or corruption (!prev)" likely witnessed a defect in how I
> back-patched this to v14.  I am looking into it.

Thank you for working on this!

Regarding that failure, it's more or less known issue, not related to your
commit:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures#check-pg_upgrade_fails_on_LLVM-enabled_animals_due_to_double_free_or_corruption
https://www.postgresql.org/message-id/flat/aPAl27_urHSODwRN%40paquier.xyz

Best regards,
Alexander