| From: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Jim Nasby <jnasby(at)upgrade(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 |
| Subject: | Re: Vacuum statistics |
| Date: | 2025-01-10 14:51:10 |
| Message-ID: | c328ec87-72f5-43a2-b312-f9757a495d99@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi! I thought about this problem again and I think I have a solution.
On 02.12.2024 23:12, Alena Rybakina wrote:
>> * I've read the previous discussion on how important to keep all these
>> fields regarding vacuum statistics including points by Andrei and Jim.
>> It still worrying me that statistics volume is going to burst in about
>> 3 times, but I don't have a particular proposal on how to make more
>> granular approach. I wonder if you could propose something.
We can collect statistics on databases at all times - there are less
compared to vacuum statistics of relations, but they can give enough
information that can hint that something is going wrong.
With the track_vacuum_statistics guc we can cover cases of collecting
extended and complete information: when it is enabled, we will collect
vacuum statistics on relations both: heaps and indexes.
This will not lead to a synchronicity between constant database
statistics and temporary statistics of relations, since our vacuum
statistics are cumulative and it is assumed that we will look at changes
in statistics over a certain period.
What do you think?
--
Regards,
Alena Rybakina
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-01-10 14:54:54 | Re: Adjusting hash join memory limit to handle batch explosion |
| Previous Message | jian he | 2025-01-10 14:50:32 | tests for pg_stat_progress_copy.tuples_skipped |