Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Vaibhav Jain <jainva(at)google(dot)com>, pg(at)bowt(dot)ie, andres(at)anarazel(dot)de
Subject: Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting
Date: 2026-11-14 02:17:39
Message-ID: CAN4CZFMf8KseUdOm8_AcxgHX5vh45xLGVf3KTn0d7oaRY3XCCw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 13 Nov 2026, Melanie Plageman <melanieplageman(at)gmail(dot)com> wrote:
> make this change (the -1/0 change) until we have consensus on the
> desired behavior and review of the docs change. I'm pretty sure the
> right immediate step is to make the 0 clamp work, though.

+1, the patch looks good to me.

vacuumlazy.c:1606 also uses 0 clamping correctly for new_rel_tuples
(that's a double), so at least those two will be consistent with this.
However, there it's used as a part of a sum, so I don't think we can
adjust that even on master.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-11-14 02:25:18 reindexdb: Change quoting rule of --schema?
Previous Message Henson Choi 2026-11-14 02:09:11 Re: Add wait events for server logging destination writes