From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | "Mead, Scott" <meads(at)amazon(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay |
Date: | 2023-01-23 17:23:20 |
Message-ID: | 20230123172320.cokmhkmgd3743wxc@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 2021-Feb-08, Mead, Scott wrote:
> Hello,
> I recently looked at what it would take to make a running autovacuum
> pick-up a change to either cost_delay or cost_limit. Users frequently
> will have a conservative value set, and then wish to change it when
> autovacuum initiates a freeze on a relation. Most users end up
> finding out they are in ‘to prevent wraparound’ after it has happened,
> this means that if they want the vacuum to take advantage of more I/O,
> they need to stop and then restart the currently running vacuum (after
> reloading the GUCs).
Hello, I think this has been overlooked, right? I can't find a relevant
commit, but maybe I just didn't look hard enough. I have a feeling that
this is something that we should address. If you still have the cycles,
please consider posting an updated patch and creating a commitfest
entry.
Thanks
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Someone said that it is at least an order of magnitude more work to do
production software than a prototype. I think he is wrong by at least
an order of magnitude." (Brian Kernighan)
From | Date | Subject | |
---|---|---|---|
Next Message | Sisson, David | 2023-01-23 19:26:09 | RE: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes |
Previous Message | MRO Mexico Industrial Supplies SA de CV | 2023-01-23 11:10:23 | Request for Quote ITBMRFQ23152 - Product Profiles_936878290323 |
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-01-23 17:25:45 | Re: wake up logical workers after ALTER SUBSCRIPTION |
Previous Message | David Geier | 2023-01-23 17:23:17 | Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? |