Re: Add mode column to pg_stat_progress_vacuum
От | Nathan Bossart |
---|---|
Тема | Re: Add mode column to pg_stat_progress_vacuum |
Дата | |
Msg-id | aOVjhYJmaVmFvsqH@nathan обсуждение исходный текст |
Ответ на | Re: Add mode column to pg_stat_progress_vacuum (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: Add mode column to pg_stat_progress_vacuum
|
Список | pgsql-hackers |
On Tue, Oct 07, 2025 at 10:17:38AM -0700, Masahiko Sawada wrote: > Right. I think we cannot display both things in one mode column. Since > both manual vacuums and anti-wraparound autovacuums can enter the > failsafe mode dynamically, if we show "failsafe" in the mode column, > we would lose the information "why is this vacuum running". I guess we > would need separate columns. For example, I guess that the column > showing "how is it operating under the hood" can have three values: > "normal", "aggressive" (disables VM optimization), and "failsafe" > (implies aggressive vacuum and disables many things to prioritize XID > freezing). Am I understanding correctly that your idea is to have a "reason" column that would have values like "manual", "normal autovacuum", and "autovacuum for wraparound", and a "mode" column that would have values like "normal", "agressive", and "failsafe"? I wonder if we could be even more granular for the "normal autovacuum" case and point to the reason the table was chosen. For example, was it the insert threshold, the update/delete threshold, etc.? -- nathan
В списке pgsql-hackers по дате отправления: