database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

Fix typos and grammar in docs and comments

Browse Source 
This fixes several areas of the documentation and some comments in
matters of style, grammar, or even format.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20201222041153.GK30237@telsasoft.com
This commit is contained in:
Michael Paquier
2020-12-24 17:05:49 +09:00
parent 6ecf488d91
commit 90fbf7c57d
23 changed files with 45 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -525,7 +525,7 @@ SET client_min_messages = DEBUG1;
designed to diagnose corruption without undue risk. It cannot guard
against all causes of backend crashes, as even executing the calling
query could be unsafe on a badly corrupted system. Access to <link
linkend="catalogs-overview">catalog tables</link> are performed and could
linkend="catalogs-overview">catalog tables</link> is performed and could
be problematic if the catalogs themselves are corrupted.
</para>

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

@ -4478,7 +4478,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
inherited columns are to be arranged. The count starts at 1.
</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.
</para></entry>
</row>

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

@ -321,7 +321,7 @@ SELECT c FROM test ORDER BY c ~&gt; 3 DESC LIMIT 5;
Makes a one dimensional cube.
</para>
<para>
<literal>cube(1,2)</literal>
<literal>cube(1, 2)</literal>
<returnvalue>(1),(2)</returnvalue>
</para></entry>
</row>

8
doc/src/sgml/func.sgml
View File

@ -1274,7 +1274,7 @@ repeat('Pg', 4) <returnvalue>PgPgPgPg</returnvalue>
(truncates towards zero)
</para>
<para>
<literal>div(9,4)</literal>
<literal>div(9, 4)</literal>
<returnvalue>2</returnvalue>
</para></entry>
</row>
@ -1493,7 +1493,7 @@ repeat('Pg', 4) <returnvalue>PgPgPgPg</returnvalue>
<type>bigint</type>, and <type>numeric</type>
</para>
<para>
<literal>mod(9,4)</literal>
<literal>mod(9, 4)</literal>
<returnvalue>1</returnvalue>
</para></entry>
</row>
@ -1975,7 +1975,7 @@ repeat('Pg', 4) <returnvalue>PgPgPgPg</returnvalue>
result in radians
</para>
<para>
<literal>atan2(1,0)</literal>
<literal>atan2(1, 0)</literal>
<returnvalue>1.5707963267948966</returnvalue>
</para></entry>
</row>
@ -1995,7 +1995,7 @@ repeat('Pg', 4) <returnvalue>PgPgPgPg</returnvalue>
result in degrees
</para>
<para>
<literal>atan2d(1,0)</literal>
<literal>atan2d(1, 0)</literal>
<returnvalue>90</returnvalue>
</para></entry>
</row>

8
doc/src/sgml/logicaldecoding.sgml
View File

@ -953,11 +953,11 @@ stream_commit_cb(...); &lt;-- commit of the streamed transaction
<para>
Similar to spill-to-disk behavior, streaming is triggered when the total
amount of changes decoded from the WAL (for all in-progress transactions)
exceeds limit defined by <varname>logical_decoding_work_mem</varname> setting.
At that point the largest toplevel transaction (measured by amount of memory
exceeds the limit defined by <varname>logical_decoding_work_mem</varname> setting.
At that point, the largest toplevel transaction (measured by the amount of memory
currently used for decoded changes) is selected and streamed. However, in
some cases we still have to spill to the disk even if streaming is enabled
because if we cross the memory limit but we still have not decoded the
some cases we still have to spill to disk even if streaming is enabled
because we exceed the memory threshold but still have not decoded the
complete tuple e.g., only decoded toast table insert but not the main table
insert.
</para>

4
doc/src/sgml/monitoring.sgml
View File

@ -3470,7 +3470,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
<structfield>wal_bytes</structfield> <type>numeric</type>
</para>
<para>
Total amount of WAL bytes generated
Total amount of WAL generated in bytes
</para></entry>
</row>
@ -3479,7 +3479,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
<structfield>wal_buffers_full</structfield> <type>bigint</type>
</para>
<para>
Number of times WAL data was written to the disk because WAL buffers got full
Number of times WAL data was written to disk because WAL buffers became full
</para></entry>
</row>

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

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

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

@ -29,7 +29,7 @@
<para>
Every range type has a corresponding multirange type. A multirange is
an ordered list of non-continguous, non-empty, non-null ranges. Most
an ordered list of non-contiguous, non-empty, non-null ranges. Most
range operators also work on multiranges, and they have a few functions
of their own.
</para>

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

@ -180,10 +180,10 @@ CREATE TYPE <replaceable class="parameter">name</replaceable>
The optional <replaceable class="parameter">multirange_type_name</replaceable>
parameter specifies the name of the corresponding multirange type. If not
specified, this name is chosen automatically as follows.
If range type name contains <literal>range</literal> substring, then
multirange type name is formed by replacement of the <literal>range</literal>
substring with <literal>multirange</literal> substring in the range
type name. Otherwise, multirange type name is formed by appending
If the range type name contains the substring <literal>range</literal>, then
the multirange type name is formed by replacement of the <literal>range</literal>
substring with <literal>multirange</literal> in the range
type name. Otherwise, the multirange type name is formed by appending a
<literal>_multirange</literal> suffix to the range type name.
</para>
</refsect2>

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

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

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

@ -621,7 +621,7 @@ PostgreSQL documentation
<listitem>
<para>
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
at a moderate level.
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>
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
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

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

@ -184,7 +184,7 @@ EXPLAIN EXECUTE <replaceable>name</replaceable>(<replaceable>parameter_values</r
analysis and planning of the statement, <productname>PostgreSQL</productname> will
force re-analysis and re-planning of the statement before using it
whenever database objects used in the statement have undergone
definitional (DDL) changes or the planner statistics of them have
definitional (DDL) changes or their planner statistics have
been updated since the previous use of the prepared
statement. Also, if the value of <xref linkend="guc-search-path"/> changes
from one use to the next, the statement will be re-parsed using the new

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

@ -103,7 +103,7 @@ less -x4
message text. In addition there are optional elements, the most
common of which is an error identifier code that follows the SQL spec's
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
look like a single function call in the C source code. The only parameter
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>,
the most recent <xref linkend="guc-wal-keep-size"/> megabytes of
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
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>