pgsql: Revert "Increase the default vacuum_cost_limit from 200 to 2000"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Revert "Increase the default vacuum_cost_limit from 200 to 2000"
Date: 2019-03-10 19:18:20
Message-ID: E1h33xk-0001Ok-HF@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert "Increase the default vacuum_cost_limit from 200 to 2000"

This reverts commit bd09503e633b8077822bb4daf91625b71ac16253.

Per discussion, it seems like what we should do instead is to
reduce the default value of autovacuum_vacuum_cost_delay by the
same factor. That's functionally equivalent as long as the
platform can accurately service the smaller delay request, which
should be true on anything released in the last 10 years or more.
And smaller, more-closely-spaced delays are better in terms of
providing a steady I/O load.

Discussion: https://postgr.es/m/28720.1552101086@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/52985e4fea75f1ec742742f27e246a8775c99e08

Modified Files
--------------
doc/src/sgml/config.sgml | 2 +-
src/backend/utils/init/globals.c | 2 +-
src/backend/utils/misc/guc.c | 2 +-
src/backend/utils/misc/postgresql.conf.sample | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-03-10 22:46:23 pgsql: Fix documentation on partitioning vs. foreign tables
Previous Message Tom Lane 2019-03-10 16:59:39 pgsql: Disallow NaN as a value for floating-point GUCs.