From: Ekaterina Kiryanova <e.kiryanova@postgrespro.ru>
To: pgsql-docs@lists.postgresql.org
Subject: Minor inconsistencies
Date: Fri, 7 Oct 2022 17:53:47 +0300
Message-ID: <a5180360-ec04-ac58-25ce-3d795d3d1f6c@postgrespro.ru> (raw)
Hello!
I've prepared a patch to add some missing periods and tags.
I also suggest the following change in pgbench.sgml:
- Here is some example output generated with these options:
+ Here is some example output generated with this option:
since I believe that this is the example for the --aggregate-interval
option.
Please take a look.
--
Ekaterina Kiryanova
Technical Writer
Postgres Professional
the Russian PostgreSQL Company
Attachments:
[text/x-patch] minor_inconsistencies.patch (4.1K, ../a5180360-ec04-ac58-25ce-3d795d3d1f6c@postgrespro.ru/2-minor_inconsistencies.patch)
download | inline diff:diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgmlindex 342b20ebeb..ad5245abef 100644--- a/doc/src/sgml/monitoring.sgml+++ b/doc/src/sgml/monitoring.sgml@@ -261,7 +261,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
unnecessary and can be avoided by setting
<varname>stats_fetch_consistency</varname> to <literal>none</literal>.
- You can invoke <function>pg_stat_clear_snapshot</function>() to discard the+ You can invoke <function>pg_stat_clear_snapshot()</function> to discard the
current transaction's statistics snapshot or cached values (if any). The
next use of statistical information will (when in snapshot mode) cause a
new snapshot to be built or (when in cache mode) accessed statistics to be
@@ -2131,15 +2131,15 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
</row>
<row>
<entry><literal>PgStatsDSA</literal></entry>
- <entry>Waiting for stats dynamic shared memory allocator access</entry>+ <entry>Waiting for stats dynamic shared memory allocator access.</entry>
</row>
<row>
<entry><literal>PgStatsHash</literal></entry>
- <entry>Waiting for stats shared memory hash table access</entry>+ <entry>Waiting for stats shared memory hash table access.</entry>
</row>
<row>
<entry><literal>PgStatsData</literal></entry>
- <entry>Waiting for shared memory stats data access</entry>+ <entry>Waiting for shared memory stats data access.</entry>
</row>
<row>
<entry><literal>SerializableXactHash</literal></entry>
diff --git a/doc/src/sgml/ref/merge.sgml b/doc/src/sgml/ref/merge.sgmlindex e07addaea4..eddf8ed52a 100644--- a/doc/src/sgml/ref/merge.sgml+++ b/doc/src/sgml/ref/merge.sgml@@ -368,9 +368,9 @@ DELETE
An expression to assign to the column. If used in a
<literal>WHEN MATCHED</literal> clause, the expression can use values
from the original row in the target table, and values from the
- <literal>data_source</literal> row.+ <replaceable>data_source</replaceable> row.
If used in a <literal>WHEN NOT MATCHED</literal> clause, the
- expression can use values from the <literal>data_source</literal>.+ expression can use values from the <replaceable>data_source</replaceable>.
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgmlindex 40e6a50a7f..1414de8b7b 100644--- a/doc/src/sgml/ref/pgbench.sgml+++ b/doc/src/sgml/ref/pgbench.sgml@@ -229,7 +229,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d
data is generated in <command>pgbench</command> client and then
sent to the server. This uses the client/server bandwidth
extensively through a <command>COPY</command>.
- <command>pgbench</command> uses the FREEZE option with version 14 or later+ <command>pgbench</command> uses the <option>FREEZE</option> option with version 14 or later
of <productname>PostgreSQL</productname> to speed up
subsequent <command>VACUUM</command>, unless partitions are enabled.
Using <literal>g</literal> causes logging to print one message
@@ -1098,7 +1098,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d
each SQL command on a single line ending with a semicolon.
</para>
<para>
- It is assumed that pgbench scripts do not contain incomplete blocks of SQL+ It is assumed that <application>pgbench</application> scripts do not contain incomplete blocks of SQL
transactions. If at runtime the client reaches the end of the script without
completing the last transaction block, it will be aborted.
</para>
@@ -2616,7 +2616,7 @@ END;
</para>
<para>
- Here is some example output generated with these options:+ Here is some example output generated with this option:
<screen>
<userinput>pgbench --aggregate-interval=10 --time=20 --client=10 --log --rate=1000 --latency-limit=10 --failures-detailed --max-tries=10 test</userinput>
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 using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: e.kiryanova@postgrespro.ru, pgsql-docs@lists.postgresql.org
Subject: Re: Minor inconsistencies
In-Reply-To: <a5180360-ec04-ac58-25ce-3d795d3d1f6c@postgrespro.ru>
* 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