Re: pgsql: Add relallfrozen to pg_class

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add relallfrozen to pg_class
Date: 2025-03-03 16:52:40
Message-ID: CAAKRu_b9MxbXbPFLShzRxgjV3kjxCZ-GrJHVBDvioa37bTgiow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Mar 3, 2025 at 11:48 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> On Mon, Mar 3, 2025 at 11:44 AM Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >
> > 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.
>
> We use relpages and reltuples from pg_class in
> relation_needs_vacanalyze() in the same way relallfrozen is being used
> here.

Sorry reltuples only (not relpages).

- Melanie

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2025-03-03 17:44:07 pgsql: Fix broken handling of domains in atthasmissing logic.
Previous Message Andres Freund 2025-03-03 16:50:21 Re: pgsql: Add relallfrozen to pg_class