|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Bruce Momjian <bruce(at)momjian(dot)us>|
|Cc:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, basil(dot)bourque(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, pgsql-docs(at)lists(dot)postgresql(dot)org|
|Subject:||Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
[ cc'ing pgsql-docs as well ]
Bruce Momjian <bruce(at)momjian(dot)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(dot)1571941169(at)sss(dot)pgh(dot)pa(dot)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
Barring objections, I'll run around and make them all look like that.
regards, tom lane
|Next Message||Andres Freund||2019-10-24 21:17:32||Re: BUG #16073: pg_dump build crashes half way|
|Previous Message||Tom Lane||2019-10-24 18:19:29||Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql|
|Next Message||Peter Eisentraut||2019-10-25 18:50:48||Re: Use proper em and en dashes|
|Previous Message||PG Doc comments form||2019-10-24 15:17:06||Instead of using the bloom index, a parallel sequencial scan is used with this example|