Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitac86237

Browse files
committed
Fix more typos and inconsistencies in documentation
This fixes a couple of grammar mistakes, typos and inconsistencies inthe 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. Someparameter 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 arethings I bumped into.Author: Justin Pryzby, Michael PaquierReviewed-by: Tom LaneDiscussion:https://postgr.es/m/20190330224333.GQ5815@telsasoft.com
1 parent8cad5ad commitac86237

File tree

4 files changed

+14
-13
lines changed

4 files changed

+14
-13
lines changed

‎doc/src/sgml/auto-explain.sgml

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,10 +54,11 @@ LOAD 'auto_explain';
5454
<para>
5555
<varname>auto_explain.log_min_duration</varname> is the minimum statement
5656
execution time, in milliseconds, that will cause the statement's plan to
57-
be logged. Setting this to zero logs all plans. Minus-one (the default)
58-
disables logging of plans. For example, if you set it to
59-
<literal>250ms</literal> then all statements that run 250ms or longer
60-
will be logged. Only superusers can change this setting.
57+
be logged. Setting this to <literal>0</literal> logs all plans.
58+
<literal>-1</literal> (the default) disables logging of plans. For
59+
example, if you set it to <literal>250ms</literal> then all statements
60+
that run 250ms or longer will be logged. Only superusers can change this
61+
setting.
6162
</para>
6263
</listitem>
6364
</varlistentry>

‎doc/src/sgml/config.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6942,8 +6942,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
69426942
<para>
69436943
Causes each action executed by autovacuum to be logged if it ran for at
69446944
least the specified number of milliseconds. Setting this to zero logs
6945-
all autovacuum actions.Minus-one (the default) disables logging
6946-
autovacuum actions. For example, if you set this to
6945+
all autovacuum actions.<literal>-1</literal> (the default) disables
6946+
loggingautovacuum actions. For example, if you set this to
69476947
<literal>250ms</literal> then all automatic vacuums and analyzes that run
69486948
250ms or longer will be logged. In addition, when this parameter is
69496949
set to any value other than <literal>-1</literal>, a message will be

‎doc/src/sgml/protocol.sgml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -811,7 +811,7 @@ BEGIN;
811811
INSERT INTO mytable VALUES(1);
812812
COMMIT;
813813
INSERT INTO mytable VALUES(2);
814-
SELCT 1/0;
814+
SELECT 1/0;
815815
</programlisting>
816816
then none of the statements would get run, resulting in the visible
817817
difference that the first <command>INSERT</command> is not committed.
@@ -1513,13 +1513,13 @@ SELCT 1/0;
15131513
length of the result from <function>gss_wrap()</function> as a four byte
15141514
integer in network byte order to the actual encrypted payload. Note that
15151515
the server will only accept encrypted packets from the client which are less
1516-
than16KB; <function>gss_wrap_size_limit()</function> should be used by the
1516+
than16kB; <function>gss_wrap_size_limit()</function> should be used by the
15171517
client to determine the size of the unencrypted message which will fit
15181518
within this limit and larger messages should be broken up into multiple
1519-
<function>gss_wrap()</function> calls. Typical segments are8KB of
1520-
unencrypted data, resulting in encrypted packets of slightly larger than8KB
1521-
but well within the16KB maximum. The server can be expected to not send
1522-
encrypted packets of larger than16KB to the client. To continue after
1519+
<function>gss_wrap()</function> calls. Typical segments are8kB of
1520+
unencrypted data, resulting in encrypted packets of slightly larger than8kB
1521+
but well within the16kB maximum. The server can be expected to not send
1522+
encrypted packets of larger than16kB to the client. To continue after
15231523
<literal>N</literal>, send the usual StartupMessage and proceed without
15241524
encryption.
15251525
</para>

‎doc/src/sgml/sources.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -872,7 +872,7 @@ BETTER: unrecognized node type: 42
872872
from a few platform dependent pieces.
873873
</para>
874874
<para>
875-
A few features included in the C99 standard are, at this time, not be
875+
A few features included in the C99 standard are, at this time, not
876876
permitted to be used in core <productname>PostgreSQL</productname>
877877
code. This currently includes variable length arrays, intermingled
878878
declarations and code, <literal>//</literal> comments, universal

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp