Re: [PATCH] Doc fix for autovacuum_max_parallel_workers

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Doc fix for autovacuum_max_parallel_workers
Date: 2026-10-15 19:03:21
Message-ID: CAN12+Y+kAwzX9AADmfNw8mxo0Q9+2+oB_uLPhFzzc88K0MRSTA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hello team,
>
> The autovacuum_max_parallel_workers is missing the following line that the other relevant autovacuum parameters mention:

yes. Was worth a double check and the only ones not SIGHUP are:

autovacuum_worker_slots
autovacuum_freeze_max_age
autovacuum_multixact_freeze_max_age

> "This parameter can only be set in the postgresql.conf file or on the server command"

Makes sense to me. The wording ending with "...command line" LGTM.

--
Sami Imseih
Amazon Web Services (AWS)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-10-15 19:12:19 Showing "Table Block Fetches" in EXPLAIN ANALYZE for index-only scans
Previous Message Greg Burd 2026-10-15 19:02:40 Re: Let an ordering index scan hand its ORDER BY value to the target list