From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Henry Francisco Garcia Cortez <garcortez@gmail.com>
To: pgsql-admin@lists.postgresql.org
Cc: david.g.johnston@gmail.com
Subject: Re: autovacuum_vacuum_cost_limit
Date: Sat, 10 Apr 2021 03:43:17 +0200
Message-ID: <464b3f924e940410da74fdc254c3aba275fc5880.camel@cybertec.at> (raw)
In-Reply-To: <CAJP2v3EJWk9ZqkxoR6w8AnBEn2HOEzhbrAYsgN37HaME8me7Ww@mail.gmail.com>
References: <CAJP2v3EJWk9ZqkxoR6w8AnBEn2HOEzhbrAYsgN37HaME8me7Ww@mail.gmail.com>
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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, garcortez@gmail.com, pgsql-admin@lists.postgresql.org, david.g.johnston@gmail.com
Subject: Re: autovacuum_vacuum_cost_limit
In-Reply-To: <464b3f924e940410da74fdc254c3aba275fc5880.camel@cybertec.at>
* 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