PostgreSQL Documentation: autovacuum_max

Type:	`integer`
Défaut:	`3`
Min:	`1`
Max:	`262143`
Contexte:	`postmaster`
Redémarrer:	`true`

Sets the maximum number of simultaneously running autovacuum worker processes

Indique le nombre maximum de processus autovacuum (autre que le lanceur d'autovacuum) qui peuvent être exécutés simultanément. La valeur par défaut est 3. Ce paramètre ne peut être configuré qu'au lancement du serveur.

Docs officielle [EN]

Grâce à Communauté francophone de PostgreSQL

Recherche dans le code source

Recommandations [EN]

If you have an installation with many tables (100's to 1000's) or with some tables which autovacuum takes hours to process, you may want to add additional autovacuum workers so that multiple tables can be vacuumed at once. Be conservative, though, as each autovacuum worker will utilize a separate CPU core, memory and I/O.

By annotated.conf

Sur StackOverflow

What exactly means the collation 'de-DE-u-kn-true'
De-Identifying PHI For HIPAA
Lazily (de-)serialize JSON with EF Core
Connect to a heroku database with pgadmin
Get breakdown from de-normalized SQL table

Sur pgsql-hackers

Re: Testing autovacuum wraparound (including failsafe)
Re: Fix the description of GUC "max_locks_per_transaction" and "max_pred_locks_per_transaction" in guc_table.c
Re: Should vacuum process config file reload more often
RE: Fix the description of GUC "max_locks_per_transaction" and "max_pred_locks_per_transaction" in guc_table.c
Re: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""

autovacuum_max_workers

Recommandations [EN]

Sur StackOverflow

Sur pgsql-hackers

Commentaires