Re: VACUUM/ANALYZE double-count the backend's own pending table stats

From: Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru>
To: Manu <manuelreyesbravo(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Cc: Sebastian Webber <sebastian(at)swebber(dot)me>
Subject: Re: VACUUM/ANALYZE double-count the backend's own pending table stats
Date: 2026-10-15 07:48:32
Message-ID: F8A8C3AC-195A-442A-86FC-57EF5B114A18@localhost.localdomain
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Manu,

Thanks for the repros. I can confirm both on 18.6.

As for pinning the VACUUM case, I agree with your lean: an IMMUTABLE
function doing DML from an index expression during ANALYZE is likely
to put a committer off, and an injection point seems like too much for
a bug fix. So let's keep the VACUUM case best-effort, as it is in v2.

As for P1 and P2, would you like to take them to a separate thread
yourself? You found them and have already narrowed down where the fix
probably belongs. If you'd rather not, I'm happy to work on them, just
let me know.

--
Ilya Staroverov

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Manu 2026-10-15 07:52:59 Re: VACUUM/ANALYZE double-count the backend's own pending table stats
Previous Message Manu 2026-10-15 07:11:27 Re: VACUUM/ANALYZE double-count the backend's own pending table stats