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 20:21:09
Message-ID: CAN12+YJgJBzVqB7QgYz=BcxRHVZvrnqoK_8x9vF8gPLKsEQwkw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

I agree. It should do something similar to [1] for consistency.

[1] https://www.postgresql.org/docs/19/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE

--
Sami

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-15 20:53:30 Re: [PG19] Promotion hangs behind a backend blocked on a stuck client
Previous Message Baji Shaik 2026-10-15 19:58:50 Re: [PATCH] Doc fix for autovacuum_max_parallel_workers