Re: another autovacuum scheduling thread - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: another autovacuum scheduling thread
Date
Msg-id aRNmEPQ18qZlLowV@nathan
Whole thread Raw
In response to Re: another autovacuum scheduling thread  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: another autovacuum scheduling thread
Re: another autovacuum scheduling thread
List 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

pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Re: Optimize LISTEN/NOTIFY
Next
From: Fujii Masao
Date:
Subject: Re: Suggestion to add --continue-client-on-abort option to pgbench