| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Henry Francisco Garcia Cortez <garcortez(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Cc: | david(dot)g(dot)johnston(at)gmail(dot)com |
| Subject: | Re: autovacuum_vacuum_cost_limit |
| Date: | 2021-04-10 01:43:17 |
| Message-ID: | 464b3f924e940410da74fdc254c3aba275fc5880.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-04-10 01:50:23 | Re: autovacuum_vacuum_cost_limit |
| Previous Message | Henry Francisco Garcia Cortez | 2021-04-09 20:19:28 | autovacuum_vacuum_cost_limit |