Re: Revive num_dead_tuples column of pg_stat_progress_vacuum
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, "Andrey M. Borodin" <x4mmm@yandex-team.ru>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-06-14T00:41:37Z
Lists: pgsql-hackers
On Thu, Jun 13, 2024 at 08:38:05PM -0400, Tom Lane wrote: > Masahiko Sawada <sawada.mshk@gmail.com> writes: >> I was about to push the patch but let me confirm just in case: is it >> okay to bump the catversion even after post-beta1? > > Yes, that happens somewhat routinely. Up to RC, even after beta2. This happens routinely every year because tweaks are always required for what got committed. And that's OK to do so now. -- Michael
Commits
-
Reintroduce dead tuple counter in pg_stat_progress_vacuum.
- f1affb67055c 17.0 landed
-
Use TidStore for dead tuple TIDs storage during lazy vacuum.
- 667e65aac354 17.0 cited