Re: [PATCH] Doc fix for autovacuum_max_parallel_workers

From: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>
To: Sami Imseih <samimseih(dot)pg(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:58:50
Message-ID: CA+fm-RP8EDVt=KjTF+CreEgOpVXtES5a1yK4Nq3AObmXDkR3Yw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 15, 2026 at 2:03 PM Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> wrote:

>
> > "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.
>

Thank you for the review. Is it worth to extend the wordings to *"... ;but
the setting can be *
*overridden for individual tables by changing table storage parameters"* as
the setting
can be changed at table level using autovacuum_parallel_workers [1].

[1]
https://www.postgresql.org/docs/19/sql-createtable.html#RELOPTION-AUTOVACUUM-PARALLEL-WORKERS

Thanks,
Baji Shaik

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-10-15 20:21:09 Re: [PATCH] Doc fix for autovacuum_max_parallel_workers
Previous Message Zsolt Parragi 2026-10-15 19:54:12 Parallel TID Range Scan returns wrong results on rescan