Re: Revive num_dead_tuples column of pg_stat_progress_vacuum - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Revive num_dead_tuples column of pg_stat_progress_vacuum
Date
Msg-id CAH2-WzmyzRggrr_+yo5FrZCorwRT=LpipRgraYb=EPWYRqCH5g@mail.gmail.com
Whole thread Raw
In response to Re: Revive num_dead_tuples column of pg_stat_progress_vacuum  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Tue, Jun 18, 2024 at 8:49 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> > At least I couldn't find anywhere in the docs where we have
> > described the relationship between these columns before. Thoughts?
>
> It would be a good idea to improve the documentation, but I think that
> we cannot simply compare these two numbers since the numbers that
> these fields count are slightly different. For instance,
> pg_stat_all_tables.n_dead_tup includes the number of dead tuples that
> are going to be HOT-pruned.

This isn't a small difference. It's actually a huge one in many cases:

https://www.postgresql.org/message-id/CAH2-WzkkGT2Gt4XauS5eQOQi4mVvL5X49hBTtWccC8DEqeNfKA@mail.gmail.com

Practically speaking they're just two different things, with hardly
any fixed relationship.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: DOCS: Generated table columns are skipped by logical replication
Next
From: Alexander Korotkov
Date:
Subject: Re: Missing docs for new enable_group_by_reordering GUC