| From: | Jim Nasby <jnasby(at)upgrade(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(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-02 21:14:13 |
| Message-ID: | 0E5557BC-50FC-400F-BE96-11922C0C11EE@upgrade.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jan 2, 2025, at 2:12 PM, Sami Imseih <samimseih(at)gmail(dot)com> wrote:
>
> Alternatively, we can remove the vacuum related stats from pg_stat_all_tables,
> but that will break monitoring tools and will leave us with the (auto)analyze
> metrics alone in pg_stat_all_tables. This sounds very ugly.
While backwards compatibility is important, there’s definitely precedent for changing what shows up in the catalog. IMHO it’s better to bite the bullet and move those fields instead of having vacuum stats spread across two different views.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2025-01-02 21:16:06 | Re: Fwd: Re: A new look at old NFS readdir() problems? |
| Previous Message | Jim Nasby | 2025-01-02 21:09:04 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |