database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-21 05:21:08 +03:00
Code Activity

doc: wording improvements

Browse Source 
Discussion: https://postgr.es/m/a5180360-ec04-ac58-25ce-3d795d3d1f6c@postgrespro.ru

Author: Ekaterina Kiryanova

Backpatch-through: master
This commit is contained in:
Bruce Momjian
2023-10-27 17:23:09 -04:00
parent 5ae2087202
commit a978565ffc
13 changed files with 35 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/merge.sgml
View File

@@ -381,9 +381,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>

7
doc/src/sgml/ref/pg_basebackup.sgml
View File

@@ -422,8 +422,9 @@ PostgreSQL documentation
A compression detail string can optionally be specified.
If the detail string is an integer, it specifies the compression
level. Otherwise, it should be a comma-separated list of items,
each of the form <literal>keyword</literal> or
<literal>keyword=value</literal>.
each of the form
<replaceable>keyword</replaceable> or
<replaceable>keyword=value</replaceable>.
Currently, the supported keywords are <literal>level</literal>,
<literal>long</literal>, and <literal>workers</literal>.
The detail string cannot be used when the compression method
@@ -1019,7 +1020,7 @@ PostgreSQL documentation
</screen></para>
<para>
To create a backup of a local server with one tar file for each tablespace
To create a backup of the local server with one tar file for each tablespace
compressed with <application>gzip</application> at level 9, stored in the
directory <filename>backup</filename>:
<screen>

3
doc/src/sgml/ref/pg_receivewal.sgml
View File

@@ -281,7 +281,8 @@ PostgreSQL documentation
A compression detail string can optionally be specified. If the
detail string is an integer, it specifies the compression level.
Otherwise, it should be a comma-separated list of items, each of the
form <literal>keyword</literal> or <literal>keyword=value</literal>.
form <replaceable>keyword</replaceable> or
<replaceable>keyword=value</replaceable>.
Currently, the only supported keyword is <literal>level</literal>.
</para>
<para>

2
doc/src/sgml/ref/pg_recvlogical.sgml
View File

@@ -274,7 +274,7 @@ PostgreSQL documentation
<listitem>
<para>
Enables decoding of prepared transactions. This option may only be specified with
<option>--create-slot</option>
<option>--create-slot</option>.
</para>
</listitem>
</varlistentry>

2
doc/src/sgml/ref/pg_restore.sgml
View File

@@ -659,7 +659,7 @@ PostgreSQL documentation
<para>
Do not output commands to select table access methods.
With this option, all objects will be created with whichever
access method is the default during restore.
table access method is the default during restore.
</para>
</listitem>
</varlistentry>

9
doc/src/sgml/ref/pg_waldump.sgml
View File

@@ -117,7 +117,7 @@ PostgreSQL documentation
<term><option>--fork=<replaceable>fork</replaceable></option></term>
<listitem>
<para>
If provided, only display records that modify blocks in the given fork.
Only display records that modify blocks in the given fork.
The valid values are <literal>main</literal> for the main fork,
<literal>fsm</literal> for the free space map,
<literal>vm</literal> for the visibility map,
@@ -174,12 +174,13 @@ PostgreSQL documentation
names, and exit.
</para>
<para>
Extensions may define custom resource managers, but pg_waldump does
Extensions may define custom resource managers, but
<application>pg_waldump</application> does
not load the extension module and therefore does not recognize custom
resource managers by name. Instead, you can specify the custom
resource managers as <literal>custom###</literal> where
"<literal>###</literal>" is the three-digit resource manager ID. Names
of this form will always be considered valid.
<replaceable>###</replaceable> is the three-digit resource manager ID.
Names of this form will always be considered valid.
</para>
</listitem>
</varlistentry>

8
doc/src/sgml/ref/pgbench.sgml
View File

@@ -229,7 +229,8 @@ 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>, except on the
<literal>pgbench_accounts</literal> table if partitions are
@@ -1118,7 +1119,8 @@ 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>
@@ -2636,7 +2638,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>