| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <jnasby(at)upgrade(dot)com> |
| Cc: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, Andrei Zubkov <zubkov(at)moonset(dot)ru>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, a(dot)lepikhov(at)postgrespro(dot)ru, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: Vacuum statistics |
| Date: | 2025-01-03 19:46:25 |
| Message-ID: | CAA5RZ0sJLo9jYw4CsrWNrgB3ff52jEK-kg1r8tL_+nEhw1C+Jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I guess one question is how realistic it is to try and put everything about (auto)vacuum in a single view.
> Given the complexity, the answer to that might just be “no”. In that case leaving existing fields in pg_stat_all_tables
> is a lot more reasonable.
Agree. I also think the total_time should be in pg_stat_all_tables.
total_time is a high level metric that along with vacuum_count
can calculate average run time of vacuums on a specific table.
Everything else in the new view are more granular details.
Regards,
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Hunter | 2025-01-03 20:15:07 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
| Previous Message | Peter Geoghegan | 2025-01-03 19:43:45 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |