| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>, Nitin Motiani <nitinmotiani(at)google(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Ilyasov Ian <ianilyasov(at)outlook(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Surya Poondla <s_poondla(at)apple(dot)com> |
| Subject: | Re: Inval reliability, especially for inplace updates |
| Date: | 2025-12-18 18:30:57 |
| Message-ID: | 20251218183057.e6.nmisch@google.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-12-18 18:35:31 | Re: [PATCH] Add memory usage reporting to VACUUM VERBOSE |
| Previous Message | Zsolt Parragi | 2025-12-18 18:28:11 | Re: Custom oauth validator options |