Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iS5BD-0005VU-AH for pgsql-bugs@arkaria.postgresql.org; Tue, 05 Nov 2019 20:11:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iS5BB-0006R9-1O for pgsql-bugs@arkaria.postgresql.org; Tue, 05 Nov 2019 20:11:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iS5BA-0006Qz-Pr; Tue, 05 Nov 2019 20:11:52 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iS5B7-0003vV-N2; Tue, 05 Nov 2019 20:11:52 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1iS5B3-0003QH-6b; Tue, 05 Nov 2019 15:11:45 -0500 Date: Tue, 5 Nov 2019 15:11:45 -0500 From: Bruce Momjian To: Tom Lane Cc: Alvaro Herrera , Daniel Gustafsson , basil.bourque@gmail.com, pgsql-bugs@lists.postgresql.org, pgsql-docs@lists.postgresql.org Subject: Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented Message-ID: <20191105201145.GB32473@momjian.us> References: <20190726220242.GA16906@alvherre.pgsql> <20190727214130.bjgyv2holjng3oeb@momjian.us> <20191009014955.GA3191@momjian.us> <15882.1571942223@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15882.1571942223@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Oct 24, 2019 at 02:37:03PM -0400, Tom Lane wrote: > I think this is confusingly bad English, and it's poor exposition > because a minor detail (it must be pretty minor, if we got away > without mentioning it at all for years) is injected into the middle > of the basic statement of the variable's purpose. I think what we'd > be better off doing is to write a separate sentence mentioning the > units, in more or less the same way that we generally handle the > default value. In <14850.1571941169@sss.pgh.pa.us> I suggested > this revision for statement_timeout: > > Abort any statement that takes more than the specified duration. > If log_min_error_statement is set > to ERROR or lower, the statement that timed out > will also be logged. > If the value is specified as a plain number, it is measured in > milliseconds by default. > A value of zero (the default) disables the timeout. > > (I'm not quite sure whether the ending "by default" is worth writing > or not.) > > Barring objections, I'll run around and make them all look like that. Thanks for applying the improvement in your patch cfb7559083. I was torn between it being a minor issue and not wanting to devote a new sentence about it, which is why I awkwardly used parentheses. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +