pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: basil.bourque@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
Date: Thu, 24 Oct 2019 14:37:03 -0400
Message-ID: <15882.1571942223@sss.pgh.pa.us> (raw)
In-Reply-To: <20191009014955.GA3191@momjian.us>
References: <C6E10B26-97E0-4B4D-9AEE-E26A7E2263F9@yesql.se>
	<20190726220242.GA16906@alvherre.pgsql>
	<20190727214130.bjgyv2holjng3oeb@momjian.us>
	<20191009014955.GA3191@momjian.us>

[ cc'ing pgsql-docs as well ]

Bruce Momjian <bruce@momjian.us> writes:
> I applied a modified version of this patch.  I didn't backpatch it past
> PG 12 because earlier releases were just too different.

I happened to stumble across the effects of this patch while trying
to improve our explanation of statement_timeout.  I follow the goal
of explaining what the default units are, but I really dislike the
way you did it:

+        Abort any statement that takes more than the specified duration
+        (defaults to milliseconds), starting from the time the command arrives at the server
         from the client. ...

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 <varname>log_min_error_statement</varname> is set
        to <literal>ERROR</literal> 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.

			regards, tom lane





view thread (7+ messages)  latest in thread

Message-ID: <15882.1571942223@sss.pgh.pa.us>
Permalink:  ../15882.1571942223@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15882.1571942223@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, alvherre@2ndquadrant.com, daniel@yesql.se, basil.bourque@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  In-Reply-To: <15882.1571942223@sss.pgh.pa.us>
  References: <C6E10B26-97E0-4B4D-9AEE-E26A7E2263F9@yesql.se> <20190726220242.GA16906@alvherre.pgsql> <20190727214130.bjgyv2holjng3oeb@momjian.us> <20191009014955.GA3191@momjian.us> <15882.1571942223@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox