mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Improve some grammar and sentences

Browse Source 
90fbf7c has taken care of that for HEAD.  This includes the portion of
the fixes that applies to the documentation, where needed depending on
the branch.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20201227202604.GC26311@telsasoft.com
Backpatch-through: 9.5
This commit is contained in:
Michael Paquier 2020-12-29 18:18:59 +09:00
parent d05e14d786
commit 5253906fac
7 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/catalogs.sgml
View File

@ -4466,7 +4466,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
inherited columns are to be arranged. The count starts at 1. inherited columns are to be arranged. The count starts at 1.
</para> </para>
<para> <para>
Indexes can not have multiple inheritance, since they can only inherit Indexes cannot have multiple inheritance, since they can only inherit
when using declarative partitioning. when using declarative partitioning.
</para></entry> </para></entry>
</row> </row>

2
doc/src/sgml/pgstatstatements.sgml
View File

@ -358,7 +358,7 @@
<structfield>wal_bytes</structfield> <type>numeric</type> <structfield>wal_bytes</structfield> <type>numeric</type>
</para> </para>
<para> <para>
Total amount of WAL bytes generated by the statement Total amount of WAL generated by the statement in bytes
</para></entry> </para></entry>
</row> </row>
</tbody> </tbody>

6
doc/src/sgml/ref/explain.sgml
View File

@ -198,9 +198,9 @@ ROLLBACK;
<listitem> <listitem>
<para> <para>
Include information on WAL record generation. Specifically, include the Include information on WAL record generation. Specifically, include the
number of records, number of full page images (fpi) and amount of WAL number of records, number of full page images (fpi) and the amount of WAL
bytes generated. In text format, only non-zero values are printed. This generated in bytes. In text format, only non-zero values are printed.
parameter may only be used when <literal>ANALYZE</literal> is also This parameter may only be used when <literal>ANALYZE</literal> is also
enabled. It defaults to <literal>FALSE</literal>. enabled. It defaults to <literal>FALSE</literal>.
</para> </para>
</listitem> </listitem>

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

@ -630,7 +630,7 @@ PostgreSQL documentation
<listitem> <listitem>
<para> <para>
Specify the compression level to use. Zero means no compression. Specify the compression level to use. Zero means no compression.
For the custom archive format, this specifies compression of For the custom and directory archive formats, this specifies compression of
individual table-data segments, and the default is to compress individual table-data segments, and the default is to compress
at a moderate level. at a moderate level.
For plain text output, setting a nonzero compression level causes For plain text output, setting a nonzero compression level causes

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

@ -40,7 +40,7 @@ PostgreSQL documentation
<para> <para>
It is important to note that the validation which is performed by It is important to note that the validation which is performed by
<application>pg_verifybackup</application> does not and can not include <application>pg_verifybackup</application> does not and cannot include
every check which will be performed by a running server when attempting every check which will be performed by a running server when attempting
to make use of the backup. Even if you use this tool, you should still to make use of the backup. Even if you use this tool, you should still
perform test restores and verify that the resulting databases work as perform test restores and verify that the resulting databases work as

2
doc/src/sgml/sources.sgml
View File

@ -103,7 +103,7 @@ less -x4
message text. In addition there are optional elements, the most message text. In addition there are optional elements, the most
common of which is an error identifier code that follows the SQL spec's common of which is an error identifier code that follows the SQL spec's
SQLSTATE conventions. SQLSTATE conventions.
<function>ereport</function> itself is just a shell macro, that exists <function>ereport</function> itself is just a shell macro that exists
mainly for the syntactic convenience of making message generation mainly for the syntactic convenience of making message generation
look like a single function call in the C source code. The only parameter look like a single function call in the C source code. The only parameter
accepted directly by <function>ereport</function> is the severity level. accepted directly by <function>ereport</function> is the severity level.

2
doc/src/sgml/wal.sgml
View File

@ -580,7 +580,7 @@
Independently of <varname>max_wal_size</varname>, Independently of <varname>max_wal_size</varname>,
the most recent <xref linkend="guc-wal-keep-size"/> megabytes of the most recent <xref linkend="guc-wal-keep-size"/> megabytes of
WAL files plus one additional WAL file are WAL files plus one additional WAL file are
kept at all times. Also, if WAL archiving is used, old segments can not be kept at all times. Also, if WAL archiving is used, old segments cannot be
removed or recycled until they are archived. If WAL archiving cannot keep up removed or recycled until they are archived. If WAL archiving cannot keep up
with the pace that WAL is generated, or if <varname>archive_command</varname> with the pace that WAL is generated, or if <varname>archive_command</varname>
fails repeatedly, old WAL files will accumulate in <filename>pg_wal</filename> fails repeatedly, old WAL files will accumulate in <filename>pg_wal</filename>