pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Mead, Scott <meads@amazon.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
Date: Mon, 23 Jan 2023 18:23:20 +0100
Message-ID: <20230123172320.cokmhkmgd3743wxc@alvherre.pgsql> (raw)
In-Reply-To: <0A3F8A3C-4328-4A4B-80CF-14CEBE0B695D@amazon.com>

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)





view thread (11+ messages)  latest in thread

Message-ID: <20230123172320.cokmhkmgd3743wxc@alvherre.pgsql>
Permalink:  ../20230123172320.cokmhkmgd3743wxc@alvherre.pgsql/
Also on:    postgresql.org/message-id/20230123172320.cokmhkmgd3743wxc@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: alvherre@alvh.no-ip.org, meads@amazon.com, pgsql-hackers@postgresql.org
  Subject: Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
  In-Reply-To: <20230123172320.cokmhkmgd3743wxc@alvherre.pgsql>
  References: <0A3F8A3C-4328-4A4B-80CF-14CEBE0B695D@amazon.com> <20230123172320.cokmhkmgd3743wxc@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox