Message-ID: <464b3f924e940410da74fdc254c3aba275fc5880.camel@cybertec.at>
Subject: Re: autovacuum_vacuum_cost_limit
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Henry Francisco Garcia Cortez <garcortez@gmail.com>,
	pgsql-admin@lists.postgresql.org
Cc: david.g.johnston@gmail.com
Date: Sat, 10 Apr 2021 03:43:17 +0200
In-Reply-To: 
 <CAJP2v3EJWk9ZqkxoR6w8AnBEn2HOEzhbrAYsgN37HaME8me7Ww@mail.gmail.com>
References: 
	<CAJP2v3EJWk9ZqkxoR6w8AnBEn2HOEzhbrAYsgN37HaME8me7Ww@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/464b3f924e940410da74fdc254c3aba275fc5880.camel%40cybertec.at>
Precedence: bulk

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.

If the three autovacuum workers allowed by autovacuum_max_workers are already enough
to strain your I/O resources, consider getting more powerful storage.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com