| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Junwang Zhao <zhjwpku(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Introduce some randomness to autovacuum |
| Date: | 2025-04-30 16:38:08 |
| Message-ID: | CAA5RZ0uTQGabav4vSTcrOTO-X9bX1A8E=xaqq1CEupcjxzN2Hg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> - Spinning. Running repeatedly on the same table but not accomplishing
> anything useful.
> But more importantly, IMHO it masks the problems instead of
> solving them more directly, and it could mask future problems, too
To add more to Nathan's comment about masking future problems,
this will not solve the "spinning" problem because if the most common
reason for this is a long-running transaction, etc., all your tables will
eventually end up with wasted vacuum cycles because the xmin
horizon is not advancing.
--
Sami Imseih
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-04-30 17:06:35 | Re: Introduce some randomness to autovacuum |
| Previous Message | vignesh C | 2025-04-30 16:31:11 | Re: Add an option to skip loading missing publication to avoid logical replication failure |