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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: basil(dot)bourque(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
Date: 2019-07-17 16:03:09
Message-ID: C6E10B26-97E0-4B4D-9AEE-E26A7E2263F9@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-docs

> On 16 Jul 2019, at 18:26, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>
> 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
> 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.

The description of the setting contains "The default value is 2 milliseconds.”
which to me implies that the unit is measured in milliseconds. If we want to
spell it out, we could add the unit like how many other on the same page does:

- Specifies the cost delay value that will be used in automatic
+ Specifies the cost delay value (in milliseconds) that will be used in automatic

cheers ./daniel

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message jack chen 2019-07-17 18:11:28 transaction and insert
Previous Message Daniel Gustafsson 2019-07-17 15:40:25 Re: BUG #15908: Xpath operations fail

Browse pgsql-docs by date

  From Date Subject
Next Message Fabien COELHO 2019-07-17 18:12:02 Re: SPITupleTable members missing in docs
Previous Message Daniel Gustafsson 2019-07-17 11:55:56 Re: SPITupleTable members missing in docs