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

From: Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru>
To: João Rito <joaovictor(dot)rito(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Manu <manuelreyesbravo(at)gmail(dot)com>, "sebastian(at)swebber(dot)me" <sebastian(at)swebber(dot)me>
Subject: Re: VACUUM/ANALYZE double-count the backend's own pending table stats
Date: 2026-11-13 07:34:10
Message-ID: 22208BD6-9D67-4744-A219-FAAC196C53A0@localhost.localdomain
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Joao,

Thanks for the scripts and the additional checks. The SAVEPOINT
placement clarifies the 305, and the E2b/E2c comparisons help explain
the reset case. I agree that these results do not indicate an
additional issue with v2.

--
Ilya Staroverov

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Michael Paquier 2026-11-13 06:58:15 Re: BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point