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

From Andrey M. Borodin
Subject Re: Revive num_dead_tuples column of pg_stat_progress_vacuum
Date
Msg-id AE42BBD3-D2C6-40E9-81D7-B052205E24C7@yandex-team.ru
Whole thread Raw
In response to Revive num_dead_tuples column of pg_stat_progress_vacuum  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Revive num_dead_tuples column of pg_stat_progress_vacuum
List pgsql-hackers

> On 4 Jun 2024, at 00:26, Masahiko Sawada <sawada.mshk@gmail.com> wrote:

Thank you! Vacuum enhancement is a really good step forward, and this small change would help a lot of observability
tools.


> On 4 Jun 2024, at 00:49, Peter Geoghegan <pg@bowt.ie> wrote:
>
> Can we rename this to num_dead_item_ids (or something similar) in
> passing?

I do not insist, but many tools will have to adapt to this change [0,1]. However, most of tools will have to deal with
removedmax_dead_tuples anyway [2], so this is not that big problem. 


Best regards, Andrey Borodin.

[0] https://github.com/jalexandre0/pgmetrics/blob/61cb150f6d1e535513a6a07fc0c6d751fbed517e/collector/collect.go#L1289
[1]
https://github.com/DataDog/integrations-core/blob/250553f3b91d25de28add93afeb929e2abf67e53/postgres/datadog_checks/postgres/util.py#L517
[2] https://github.com/search?q=num_dead_tuples+language%3AGo&type=code


pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Logical Replication of sequences
Next
From: Ashutosh Bapat
Date:
Subject: Re: apply_scanjoin_target_to_paths and partitionwise join