| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, Frédéric Yhuel <frederic(dot)yhuel(at)dalibo(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Michael Banck <mbanck(at)gmx(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New GUC autovacuum_max_threshold ? |
| Date: | 2025-01-14 02:09:05 |
| Message-ID: | Z4XHQR6_AVKiyFjG@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 13, 2025 at 05:17:11PM -0600, Sami Imseih wrote:
> I propose renaming the GUC from "autovacuum_max_threshold" to
> "autovacuum_vacuum_max_threshold" to clarify that it applies only
> to the vacuum operation performed by autovacuum, not to the analyze operation.
> This will also align with naming for other related GUCs, i.e.,
> "autovacuum_analyze_threshold" and "autovacuum_vacuum_threshold."
>
> The "vacuum threshold" calculation described in [1] will also need to be
> updated.
Good call. Here is an updated patch.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Introduce-autovacuum_vacuum_max_threshold.patch | text/plain | 11.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2025-01-14 02:13:10 | Re: Some ExecSeqScan optimizations |
| Previous Message | Tom Lane | 2025-01-14 02:02:38 | Re: Several buildfarm animals fail tests because of shared memory error |