| From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add relallfrozen to pg_class |
| Date: | 2025-03-03 16:44:54 |
| Message-ID: | 202503031644.nihftaytey2b@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 2025-Mar-03, Melanie Plageman wrote:
> Add relallfrozen to pg_class
>
> Add relallfrozen, an estimate of the number of pages marked all-frozen
> in the visibility map.
>
> pg_class already has relallvisible, an estimate of the number of pages
> in the relation marked all-visible in the visibility map. This is used
> primarily for planning.
>
> relallfrozen, together with relallvisible, is useful for estimating the
> outstanding number of all-visible but not all-frozen pages in the
> relation for the purposes of scheduling manual VACUUMs and tuning vacuum
> freeze parameters.
I'm confused about this. Why was the new value added to pg_class
instead of to the pgstat system? I don't think relallvisible is a good
precedent, because as you write here, that one is used for planning,
which has different requirements. For vacuuming metrics we rely on
pgstat.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"El número de instalaciones de UNIX se ha elevado a 10,
y se espera que este número aumente" (UPM, 1972)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-03-03 16:48:18 | Re: pgsql: Add relallfrozen to pg_class |
| Previous Message | Melanie Plageman | 2025-03-03 16:44:02 | Re: pgsql: Set amcancrosscompare to true for hash |