Fix more typos and inconsistencies in documentation

This fixes a couple of grammar mistakes, typos and inconsistencies in
the documentation.  Particularly, the configuration parsing allows only
"kB" to mean kilobyte but there were references in the docs to "KB".
Some instances of the latter are still in the code comments.  Some
parameter values were mentioned with "Minus-one", and using directly
"-1" with proper markups is more helpful to the reader.

Some of these have been pointed out by Justin, and some others are
things I bumped into.

Author: Justin Pryzby, Michael Paquier
Reviewed-by: Tom Lane
Discussion: https://postgr.es/m/20190330224333.GQ5815@telsasoft.com
This commit is contained in:
Michael Paquier 2019-04-28 22:53:33 +09:00
parent 8cad5adb9c
commit ac86237603
4 changed files with 14 additions and 13 deletions

View File

@ -54,10 +54,11 @@ LOAD 'auto_explain';
<para>
<varname>auto_explain.log_min_duration</varname> is the minimum statement
execution time, in milliseconds, that will cause the statement's plan to
be logged. Setting this to zero logs all plans. Minus-one (the default)
disables logging of plans. For example, if you set it to
<literal>250ms</literal> then all statements that run 250ms or longer
will be logged. Only superusers can change this setting.
be logged. Setting this to <literal>0</literal> logs all plans.
<literal>-1</literal> (the default) disables logging of plans. For
example, if you set it to <literal>250ms</literal> then all statements
that run 250ms or longer will be logged. Only superusers can change this
setting.
</para>
</listitem>
</varlistentry>

View File

@ -6942,8 +6942,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<para>
Causes each action executed by autovacuum to be logged if it ran for at
least the specified number of milliseconds. Setting this to zero logs
all autovacuum actions. Minus-one (the default) disables logging
autovacuum actions. For example, if you set this to
all autovacuum actions. <literal>-1</literal> (the default) disables
logging autovacuum actions. For example, if you set this to
<literal>250ms</literal> then all automatic vacuums and analyzes that run
250ms or longer will be logged. In addition, when this parameter is
set to any value other than <literal>-1</literal>, a message will be

View File

@ -811,7 +811,7 @@ BEGIN;
INSERT INTO mytable VALUES(1);
COMMIT;
INSERT INTO mytable VALUES(2);
SELCT 1/0;
SELECT 1/0;
</programlisting>
then none of the statements would get run, resulting in the visible
difference that the first <command>INSERT</command> is not committed.
@ -1513,13 +1513,13 @@ SELCT 1/0;
length of the result from <function>gss_wrap()</function> as a four byte
integer in network byte order to the actual encrypted payload. Note that
the server will only accept encrypted packets from the client which are less
than 16KB; <function>gss_wrap_size_limit()</function> should be used by the
than 16kB; <function>gss_wrap_size_limit()</function> should be used by the
client to determine the size of the unencrypted message which will fit
within this limit and larger messages should be broken up into multiple
<function>gss_wrap()</function> calls. Typical segments are 8KB of
unencrypted data, resulting in encrypted packets of slightly larger than 8KB
but well within the 16KB maximum. The server can be expected to not send
encrypted packets of larger than 16KB to the client. To continue after
<function>gss_wrap()</function> calls. Typical segments are 8kB of
unencrypted data, resulting in encrypted packets of slightly larger than 8kB
but well within the 16kB maximum. The server can be expected to not send
encrypted packets of larger than 16kB to the client. To continue after
<literal>N</literal>, send the usual StartupMessage and proceed without
encryption.
</para>

View File

@ -872,7 +872,7 @@ BETTER: unrecognized node type: 42
from a few platform dependent pieces.
</para>
<para>
A few features included in the C99 standard are, at this time, not be
A few features included in the C99 standard are, at this time, not
permitted to be used in core <productname>PostgreSQL</productname>
code. This currently includes variable length arrays, intermingled
declarations and code, <literal>//</literal> comments, universal