Revert "Increase the default vacuum_cost_limit from 200 to 2000"
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 10 Mar 2019 19:05:25 +0000 (15:05 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 10 Mar 2019 19:05:25 +0000 (15:05 -0400)
commit52985e4fea75f1ec742742f27e246a8775c99e08
tree62fa920f72ec9b5b92e0562c46a1a1619b2ec478
parentcaf626b2cd471615914986f18282c03c8282a1f4
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
doc/src/sgml/config.sgml
src/backend/utils/init/globals.c
src/backend/utils/misc/guc.c
src/backend/utils/misc/postgresql.conf.sample