Re: pg15: reltuples stuck at -1 after pg_upgrade and VACUUM - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: pg15: reltuples stuck at -1 after pg_upgrade and VACUUM
Date
Msg-id CAH2-WznWY5buXOHxan5ATfhptCUmZwA=htrkm_Fj-TFsNfG6fg@mail.gmail.com
Whole thread Raw
In response to pg15: reltuples stuck at -1 after pg_upgrade and VACUUM  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: pg15: reltuples stuck at -1 after pg_upgrade and VACUUM
List pgsql-hackers
On Tue, Aug 8, 2023 at 8:43 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> The problem isn't that reltuples == -1 after the upgrade (which is
> normal).  The issue is that if VACUUM skips all the pages, it can leave
> reltuples -1.  My expectation is that after running "vacuum", no tables
> are left in the "never have been vacuumed" state.

But -1 isn't the "never have been vacuumed" state, exactly. At best it
is the "never been vacuumed or analyzed" state.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Junwang Zhao
Date:
Subject: [BackendXidGetPid] only access allProcs when xid matches
Next
From: Amit Kapila
Date:
Subject: Re: [PoC] pg_upgrade: allow to upgrade publisher node