diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/auto-explain.sgml | 9 | ||||
| -rw-r--r-- | doc/src/sgml/config.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/protocol.sgml | 12 | ||||
| -rw-r--r-- | doc/src/sgml/sources.sgml | 2 |
4 files changed, 14 insertions, 13 deletions
diff --git a/doc/src/sgml/auto-explain.sgml b/doc/src/sgml/auto-explain.sgml index da16164387a..3d619d4a3dd 100644 --- a/doc/src/sgml/auto-explain.sgml +++ b/doc/src/sgml/auto-explain.sgml @@ -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> diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index dbe3026d051..8ddab75b5ab 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -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 diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 4c4bb38ba7f..f6b5bfc131c 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -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> diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml index 419f753c7bc..a339ebbc4ba 100644 --- a/doc/src/sgml/sources.sgml +++ b/doc/src/sgml/sources.sgml @@ -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 |