| Type: | integer |
| Default: | -1 (-1) |
| Min: | -1 (-1) |
| Max: | 2147483647 (2147483647kB) |
| Unit: | KB |
| Context: | sighup |
| Restart: | false |
| Since: | 9.4 |
Specifies the maximum amount of memory to be used by each autovacuum worker process. If this value is specified without units, it is taken as kilobytes. It defaults to -1, indicating that the value of maintenance_work_mem should be used instead. The setting has no effect on the behavior of VACUUM when run in other contexts. This parameter can only be set in the postgresql.conf file or on the server command line.
Recommendations
Set a limit on this which is based on the number of autovac workers you expect to have running.
On StackOverflow
On pgsql-hackers
- bgwrite process is too lazy
- A thousand pg_commit_ts truncate attempts per second, two restarting autovacuum processes, and a explosive replication lag. Oh my.
- Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
- Re: New GUC autovacuum_max_threshold ?
- Re: Increase of maintenance_work_mem limit in 64-bit Windows