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-19 16:36:42
Message-ID: CAAKRu_bp9pPytgGc2Fw4Zs0CMr12gRokbLtcUs=N78vjE=uaAw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 18, 2026 at 4:38 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> On Wed, Nov 18, 2026 at 12:21 PM Lukas Fittl <lukas(at)fittl(dot)com> wrote:
> >
> > Personally I still think returning NULL is the better choice on master
> > - its easy enough to update for a client program, and I think 0 is
> > ambiguous (so we should try to get away from that ambiguity over
> > time).
>
> Cool. I'll commit the attached tomorrow then.

Done.

- Melanie

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ishjaap Singh 2026-11-19 16:37:08 Re: psql: Don't offer partitioned tables after CREATE INDEX CONCURRENTLY
Previous Message Andrew Dunstan 2026-11-19 16:34:27 Table AM callback for logical decoding support (REPACK CONCURRENTLY)