title: Postgres - Configuration Change to Vacuum Requires Restart?
body: <p>In the postgressql.conf file, I'd like to turn on autovacuum and change the threshold to 100. Because changing the max_workers thread explicitly states that it requires a restart, I am inferring that turning authvacuum on and changing its threshold does not. Can someone confirm?  </p>
  
  <pre><code>autovacuum = on         # Enable autovacuum subprocess?  'on'
                      # requires track_counts to also be on.
  #log_autovacuum_min_duration = -1   # -1 disables, 0 logs all actions and
                  # their durations, &gt; 0 logs only
                  # actions running at least this number
                  # of milliseconds.
  #autovacuum_max_workers = 3     # max number of autovacuum subprocesses
                  # **(change requires restart)**
  #autovacuum_naptime = 1min      # time between autovacuum runs
  autovacuum_vacuum_threshold = 100   # min number of row updates before
                  # vacuum
  </code></pre>
  
  <p>However, in the following post I found evidence for the opposite inference; note that effective_cache_size explicitly states that a restart is not required while autovacuum does not mention a restart:
  <a href="https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server" rel="nofollow">https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server</a></p>