| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Sami Imseih <samimseih(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: another autovacuum scheduling thread |
| Date: | 2025-11-11 16:36:32 |
| Message-ID: | aRNmEPQ18qZlLowV@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Still catching up on the latest discussion, but here's a v8 patch that
amends the DEBUG3 in relation_needs_vacanalyze() to also log the score. I
might attempt to add some sort of brief documentation about autovacuum
prioritization next.
From skimming the latest discussion, I gather we might want to consider
re-sorting the list periodically. Is the idea that we'll re-sort the
remaining tables in the list, or that we'll basically restart
do_autovacuum()? If it's the latter, then we'll need to come up with some
way to decide when to stop for the current database. Right now, we just go
through pg_class and call it a day.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v8-0001-autovacuum-scheduling-improvements.patch | text/plain | 13.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-11-11 16:47:37 | Re: Suggestion to add --continue-client-on-abort option to pgbench |
| Previous Message | Joel Jacobson | 2025-11-11 16:34:39 | Re: Optimize LISTEN/NOTIFY |