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

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Lukas Fittl <lukas(at)fittl(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, 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-18 16:06:07
Message-ID: CAAKRu_Yv_aOMVH29TJwkU9Wz2VRWo9=BbRNmCmSQbsqcaDsK_Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 14, 2026 at 11:23 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> I'll commit this specific patch after the 19 freeze is over to go out
> with the next set of minors. Thanks again for the timely review and
> apologies for not getting it out in time. I can then apply the change
> to make it NULL on master afterward, assuming we think that's the
> right thing to do.

I've committed the fix and backpatched it. The question is whether we
want master to return NULL when there was not enough information to
make an estimate for approx_tuple_count.

- Melanie

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-11-18 16:16:21 Re: Assertion failure with temporary relations in single-user mode
Previous Message Heikki Linnakangas 2026-11-18 15:42:01 Re: [RFC] An ETW backend for the static probes on Windows