Re: Should we increase the default vacuum_cost_limit?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gavin Flower <GavinFlower@archidevsys.co.nz>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
David Rowley <david.rowley@2ndquadrant.com>,
Jeff Janes <jeff.janes@gmail.com>,
Jeremy Schneider <schnjere@amazon.com>,
Joe Conway <mail@joeconway.com>, Peter Geoghegan <pg@bowt.ie>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-03-09T21:06:33Z
Lists: pgsql-hackers
Gavin Flower <GavinFlower@archidevsys.co.nz> writes: > Hope about keeping the default unit of ms, but converting it to a > 'double' for input, but storing it as int (or long?) number of > nanoseconds. Gives finer grain of control withouthaving to specify a > unit, while still allowing calculations to be fast? Don't really see the point. The only places where we do any calculations with the value are where we're about to sleep, so shaving a few nanosec doesn't seem very interesting. regards, tom lane
Commits
-
Allow fractional input values for integer GUCs, and improve rounding logic.
- 1a83a80a2fe5 12.0 landed
-
Reduce the default value of autovacuum_vacuum_cost_delay to 2ms.
- cbccac371c79 12.0 landed
-
Revert "Increase the default vacuum_cost_limit from 200 to 2000"
- 52985e4fea75 12.0 landed
-
Convert [autovacuum_]vacuum_cost_delay into floating-point GUCs.
- caf626b2cd47 12.0 landed
-
Include GUC's unit, if it has one, in out-of-range error messages.
- 28a65fc3607a 12.0 landed
-
Disallow NaN as a value for floating-point GUCs.
- ac75959cdc07 12.0 landed
- f9ec64df8f25 10.8 landed
- e04bb261633d 9.4.22 landed
- d8f8183c0467 9.5.17 landed
- bc2232f2f544 11.3 landed
- 5aafedc2fdbd 9.6.13 landed
-
Increase the default vacuum_cost_limit from 200 to 2000
- bd09503e633b 12.0 landed