| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> |
| Cc: | Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Doc fix for autovacuum_max_parallel_workers |
| Date: | 2026-10-15 23:34:42 |
| Message-ID: | CAHGQGwH3JrgcoWuCApBZRtCsuphO9Fz=p7viScXhLz2ZbsnLvA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 16, 2026 at 7:01 AM Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> wrote:
> v3 updated with the recommendation.
+ line; but the setting can be overridden for individual tables by
"overridden" should be "reduced" here? IIUC, this GUC remains an upper limit
even when the table storage parameter is set, so the table parameter can
lower the limit but cannot raise it. Both autovacuum_freeze_max_age and
autovacuum_multixact_freeze_max_age seem to use "reduced" for the same
reason.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-10-15 23:44:45 | Re: Revert libpq servicefile connection option in v19 (info leak and uninterruptible backend DoS) |
| Previous Message | Sehrope Sarkuni | 2026-10-15 23:17:18 | Revert libpq servicefile connection option in v19 (info leak and uninterruptible backend DoS) |