BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: basil(dot)bourque(at)gmail(dot)com
Subject: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
Date: 2019-07-16 16:26:54
Message-ID: 15912-2e35e9026f61230b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-docs

The following bug has been logged on the website:

Bug reference: 15912
Logged by: Basil Bourque
Email address: basil(dot)bourque(at)gmail(dot)com
PostgreSQL version: 12beta2
Operating system: macOS

The `autovacuum_vacuum_cost_delay` setting:


…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.


Browse pgsql-bugs by date

  From Date Subject
Next Message Manuel Rigger 2019-07-16 16:33:08 Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2
Previous Message Alexander Lakhin 2019-07-16 16:24:56 Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly

Browse pgsql-docs by date

  From Date Subject
Next Message Daniel Gustafsson 2019-07-17 11:55:56 Re: SPITupleTable members missing in docs
Previous Message EMS 2019-07-16 06:56:52 RE:生成采购建议 - 推荐参考:[EMS335011234] /优先/客户参考:[EMS]