Re: Inval reliability, especially for inplace updates - Mailing list pgsql-hackers

On Wed, Dec 17, 2025 at 07:00:00AM +0200, Alexander Lakhin wrote:
> 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

Since v14 dragonet had never failed before, I was ready to assume it was new.
Thank you for highlighting the older issue.  I agree.

Other buildfarm failures have been either abi-compliance-check (expected) or
unrelated, so I've closed https://commitfest.postgresql.org/patch/5091/.  That
finishes the known-reachable inplace update corruption routes.