| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add mode column to pg_stat_progress_vacuum |
| Date: | 2025-08-14 12:20:07 |
| Message-ID: | CALdSSPhrT6CVC77gWdU=+_BAf8DavHmiS-8dZSfK4rpxpL363w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 14 Aug 2025 at 16:13, Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> wrote:
> This patch introduces a mode column to provide this visibility. The
> possible values are:
> - normal: A standard, user-initiated VACUUM or a regular autovacuum run.
> - anti-wraparound: An autovacuum run launched specifically to prevent
> transaction ID wraparound.
> - failsafe: A vacuum that has entered failsafe mode to prevent
> imminent transaction ID wraparound.
> Thought?
Just a small comment:
I am more used to Lazy vs Eager vacuum types. It is how we use to call
them in doc and code. Maybe this wording will be better?
--
Best regards,
Kirill Reshke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-08-14 12:30:51 | Re: cfbot mistakenly reports that a rebase is needed |
| Previous Message | Hayato Kuroda (Fujitsu) | 2025-08-14 12:12:44 | RE: Make pgoutput documentation easier to find |