Re: another autovacuum scheduling thread
| От | Nathan Bossart |
|---|---|
| Тема | Re: another autovacuum scheduling thread |
| Дата | |
| Msg-id | acRROBvlokDLQZlh@nathan обсуждение исходный текст |
| Ответ на | Re: another autovacuum scheduling thread (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
| Ответы |
Re: another autovacuum scheduling thread
Re: another autovacuum scheduling thread |
| Список | pgsql-hackers |
On Wed, Mar 25, 2026 at 02:12:16PM -0700, Bharath Rupireddy wrote: > Would it make sense to recompute scores and re-sort the remaining > table list after each table is processed in do_autovacuum()'s main > loop - say, after a certain amount of time spent vacuuming the large > table(s)? This would catch the above scenarios. I see that the scores > per table are being calculated in relation_needs_vacanalyze, but they > are ignored in the recheck path (table_recheck_autovac -> > recheck_relation_needs_vacanalyze -> relation_needs_vacanalyze). I think this was discussed a bit upthread, and we decided to leave it out for now. But things like reprioritization and automatic cost limit adjustments seem worth considering for v20. -- nathan
В списке pgsql-hackers по дате отправления: