Reintroduce dead tuple counter in pg_stat_progress_vacuum.
authorMasahiko Sawada
Fri, 14 Jun 2024 01:08:15 +0000 (10:08 +0900)
committerMasahiko Sawada
Fri, 14 Jun 2024 01:08:15 +0000 (10:08 +0900)
commitf1affb67055c9b3f31a7ee7eb521a9ba64fff488
treee2a52561fee7700bf89cc5ad6f0372d1a3d52556
parent56a8296212b68267dc2bddeb1fb40a893b1aadb3
Reintroduce dead tuple counter in pg_stat_progress_vacuum.

Commit 667e65aac3 changed both num_dead_tuples and max_dead_tuples
columns to dead_tuple_bytes and max_dead_tuple_bytes columns,
respectively. But as per discussion, the number of dead tuples
collected still provides meaningful insights for users.

This commit reintroduces the column for the count of dead tuples,
renamed as num_dead_item_ids. It avoids confusion with the number of
dead tuples removed by VACUUM, which includes dead heap-only tuples
but excludes any pre-existing LP_DEAD items left behind by
opportunistic pruning.

Bump catalog version.

Reviewed-by: Peter Geoghegan, Álvaro Herrera, Andrey Borodin
Discussion: https://postgr.es/m/CAD21AoBL5sJE9TRWPyv%2Bw7k5Ee5QAJqDJEDJBUdAaCzGWAdvZw%40mail.gmail.com
doc/src/sgml/monitoring.sgml
src/backend/access/heap/vacuumlazy.c
src/backend/catalog/system_views.sql
src/include/catalog/catversion.h
src/include/commands/progress.h
src/test/regress/expected/rules.out