| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: doc: fix pg_stat_autovacuum_scores threshold wording |
| Date: | 2026-06-26 18:26:20 |
| Message-ID: | aj7ETI0jthcmrlhq@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 25, 2026 at 10:48:07AM -0500, Sami Imseih wrote:
>> I guess that may be how the current wording came from. But it seems a
>> bit indirect to describe it that way, because the weight itself does not
>> determine if autovacuum would vacuum or analyze the table.
My goal was to explain how to interpret the value as simply as possible.
It's true that the code doesn't use this value for deciding eligibility,
but the documentation doesn't say that it does. Rather, it gives users a
frame of reference for what a given value means.
> Thanks for reporting. I took a look and agree with your doc changes.
> do_vacuum/do_analyze will not be true for cases where the
> individual component scores are less than or equal to the weight.
+1, I'll take care of it.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florents Tselai | 2026-06-26 18:28:42 | Re: More jsonpath methods: translate, split, join |
| Previous Message | Nathan Bossart | 2026-06-26 18:18:55 | Re: md5_password_warnings for password auth with MD5-encrypted passwords |