PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15912
PG Version12beta2
OSmacOS
Opened2019-07-16 16:26:54+00
Reported byBasil Bourque
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15912
Logged by:          Basil Bourque
Email address:      (redacted)
PostgreSQL version: 12beta2
Operating system:   macOS
Description:        

The `autovacuum_vacuum_cost_delay` setting:

https://www.postgresql.org/docs/devel/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY

…does not specify its units (seconds? milliseconds?) explicitly.  

Previously, one could guess that the units were milliseconds. 

But now in Postgres 12 the argument type changed from `integer` to `floating
point`. So now the units are quite unclear. I am guessing a whole number
means milliseconds, while the fractional part represents microseconds. But
that is only a guess. Should be documented.

Messages

DateAuthorSubject
2019-07-16 16:26:54+00PG Bug reporting formBUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
2019-07-17 16:03:09+00Daniel GustafssonRe: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
2019-07-26 22:02:42+00Alvaro HerreraRe: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
2019-07-27 21:41:30+00Bruce MomjianRe: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
2019-10-09 01:49:55+00Bruce MomjianRe: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
2019-10-24 18:37:03+00Tom LaneRe: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
2019-11-05 20:11:45+00Bruce MomjianRe: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented