| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
| Cc: | Masahiko Sawada <msawada(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow autovacuum to use parallel vacuum workers. |
| Date: | 2026-04-09 19:12:56 |
| Message-ID: | CAD21AoAKP=NYGzMXotD_tZZxutGwRc=38fMQ7+5NJ1XXDquV2w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Tue, Apr 7, 2026 at 4:52 AM Aleksander Alekseev
<aleksander(at)tigerdata(dot)com> wrote:
>
> Hi,
>
> > Allow autovacuum to use parallel vacuum workers.
> >
> > [...]
>
> I think there is a mistake in the documentation:
>
> ```
> + For autovacuum, it is limited by the table's
> + <xref linkend="reloption-autovacuum-parallel-workers"/> if any which is
> + capped limited by
> + <xref linkend="guc-autovacuum-max-parallel-workers"/> parameter. Please
> ```
>
> Firstly "capped limited by" almost certainly should be either "capped
> by" or "limited by". Secondly "limited by the tables's [...] if any"
> doesn't sound right. Probably what was meant is "if set".
>
> I suggest fixing it as attached.
Thank you for the report. Indeed, we need to fix the wording.
I've attached the patch based on your proposal that uses the
explanation consistent with the manual VACUUM and autovacuums. What do
you think?
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-doc-Improve-consistency-of-parallel-vacuum-descri.patch | application/octet-stream | 2.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-04-09 22:59:11 | pgsql: Enhance make_ctags and make_etags. |
| Previous Message | Nathan Bossart | 2026-04-09 18:10:26 | pgsql: Fix double-free in pg_stat_autovacuum_scores. |