| Type: | integer |
| Default: | -1 (-1) |
| Min: | -1 (-1) |
| Max: | 2147483647 (2147483647ms) |
| Unit: | milliseconds (ms) |
| Context: | sighup |
| Restart: | false |
Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. -1 (the default) disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to 250ms then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1, a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters.
Recommendations
On StackOverflow
- 100% CPU load on AWS Aurora Postgres cluster after batch-deleting records
- csvlog of postgres 13 seems to be corrupted
- Auto analyze not running for all tables in Postgres 9.2 database
- Postgresql 9.3 Autovacuum not keeping up despite aggressive settings
- Postgres - Configuration Change to Vacuum Requires Restart?
On pgsql-hackers
- Re: a verbose option for autovacuum
- Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic
- Teaching users how they can get the most out of HOT in Postgres 14
- GIN pending list cleanup during autoanalyze blocks cleanup by VACUUM
- Re: when the startup process doesn't (logging startup delays)