Jeff Bohmer wrote:
I assumed (perhaps incorrectly) that you were talking about
maintaining the data in the theoretical / not yet in existence
autovacuum stats table through database restart, the stats system
already has a GUC var that dictates whether or not it dumps it's data
upon DB restart.
AFAIK, a restart does not affect the VACUUMed-ness of anything.
Keeping these (currently nonexistent autovacuum) stats across restarts
would be helpful if stats_reset_on_server_start=on.
Unless I misunderstand, if stats_reset_on_server_start=off, these
(currently nonexistent autovacuum) stats would only be relevant for
autovacuum's VACUUM activity and not it's ANALYZE activity. In which
case, it seems ideal to keep autovacuum VACUUM stats regardless of the
GUC setting, while autovacuum ANALYZE stats should follow it. But if
the ideal is impractical, making both ANALYZE and VACUUM stats follow
the GUC would still be real nice.
I'm confused... the GUC var stats_reset_on_server_start dictates if the
stats system dumps its data on DB restart. If we added a new table to
the stats system kept track of autovacuum activity, then that data would
also be dumped on restart if stats_reset_on_server_start=true.
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
