| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add mode column to pg_stat_progress_vacuum |
| Date: | 2025-10-07 19:40:02 |
| Message-ID: | CAA5RZ0t5hrrYik1wrBK0EN19tkTcDvxy73mcFNoM92PgFhwHcg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.?
>
> Sounds like reasonable information. I guess we might want to have such
> information in a cumulative statistics view but do you think it's
> better to have it in a dynamic statistics view?
+1 for this information in cumulative stats, on a per table level for sure.
I do think however the pg_stat_all_tables views is getting too wide
and moving new relation vacuum stats to a separate stats view will
be very useful.
--
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-10-07 19:46:28 | Re: Should we update the random_page_cost default value? |
| Previous Message | Masahiko Sawada | 2025-10-07 19:34:01 | Re: Add mode column to pg_stat_progress_vacuum |