Date: Fri, 9 Apr 2021 21:50:23 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Henry Francisco Garcia Cortez <garcortez@gmail.com>,
	pgsql-admin@lists.postgresql.org, david.g.johnston@gmail.com
Subject: Re: autovacuum_vacuum_cost_limit
Message-ID: <20210410015023.GA13248@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <464b3f924e940410da74fdc254c3aba275fc5880.camel@cybertec.at>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210410015023.GA13248%40alvherre.pgsql>
Precedence: bulk

On 2021-Apr-10, Laurenz Albe wrote:

> On Fri, 2021-04-09 at 14:19 -0600, Henry Francisco Garcia Cortez wrote:
> > Hi community I have a question about autovacuum_vacuum_cost_limit
> >  I want to increase this parameter I have read on internet that value
> >  It could have as maximum 10,000 but I want to know, what will it be the troubles if I did that change 
> 
> That will keep PostgreSQL from functioning properly.
> 
> I would never increase the setting beyond the 20ms that were the
> default before v12.

I think you're confusing it with autovacuum_vacuum_cost_delay.  He is
asking about the cost_limit.  Increasing that setting will mean that the
20ms sleeps will occur much less frequently.

-- 
Álvaro Herrera       Valdivia, Chile