Re: pg15: reltuples stuck at -1 after pg_upgrade and VACUUM

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Subject: Re: pg15: reltuples stuck at -1 after pg_upgrade and VACUUM
Date: 2023-08-09 04:07:58
Message-ID: CAH2-WznWY5buXOHxan5ATfhptCUmZwA=htrkm_Fj-TFsNfG6fg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 8, 2023 at 8:43 PM Justin Pryzby <pryzby(at)telsasoft(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-08-09 04:15:15 Re: [PoC] pg_upgrade: allow to upgrade publisher node
Previous Message Junwang Zhao 2023-08-09 04:00:34 [BackendXidGetPid] only access allProcs when xid matches