BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
Date
Msg-id 15912-2e35e9026f61230b@postgresql.org
Whole thread Raw
Responses Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` settingshould be documented  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      15912
Logged by:          Basil Bourque
Email address:      basil.bourque@gmail.com
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.


pgsql-bugs by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
Next
From: Manuel Rigger
Date:
Subject: Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2