From 5ce01c9b01df8cdccbf765ba7b65b4415d1d346d Mon Sep 17 00:00:00 2001 From: Baji Shaik Date: Sun, 11 Oct 2026 20:25:54 -0500 Subject: [PATCH v4] doc: say where autovacuum_max_parallel_workers can be set The parameter is PGC_SIGHUP, like the other autovacuum settings, but unlike them its description doesn't say it can only be set in postgresql.conf or on the server command line, nor that it can be reduced per-table. Add the usual sentence, and link to the corresponding table storage parameter: the reloption is named autovacuum_parallel_workers while the GUC is autovacuum_max_parallel_workers, so the link makes the connection clear. The GUC is an upper limit; the table storage parameter can only reduce the effective number of workers, not raise it above the GUC, so the wording follows autovacuum_freeze_max_age in saying "reduced". Backpatch to 19, where the parameter was added. Author: Baji Shaik --- doc/src/sgml/config.sgml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index e537b3b0043..f7db2995c3e 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -9858,7 +9858,12 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; per-autovacuum worker equivalent of the PARALLEL option of the VACUUM command. Setting this value to 0 disables parallel vacuum during autovacuum. - The default is 0. + The default is 0. This parameter can only be set in the + postgresql.conf file or on the server command + line; but the setting can be reduced for individual tables by + changing the + corresponding + table storage parameter. -- 2.54.0 (Apple Git-157)