> Approach 2: > - log_autovacuum_min_duration: Changed behavior, which controls only > autovacuum logging. > - log_autoanalyze_min_duration: New parameter, which controls > autoanalyze logging.
My vote is for this approach. It is probably OK to change the behavior of log_autovacuum_min_duration, as the new GUC will have the same default value.
log_autoanalyze_min_duration makes sense, especially since "autoanalyze" is the term we already use in system views (e.g., pg_stat_all_tables.last_autoanalyze). I do not think we need to worry about consistency with other autovacuum parameters (e.g., autovacuum_[vacuum|analyze]_threshold, etc.), because in this case we are only talking about logging, so we have more flexibility in naming.
Initially, I was not sure if there is a use case in which someone would want to turn off autovacuum logging but keep autoanalyze logging (or vice versa), but there may be, and this will be more flexible.
