mirror of
https://github.com/postgres/postgres.git
synced 2025-07-30 11:03:19 +03:00
Fix typos in comments, code and documentation
While on it, newlines are removed from the end of two elog() strings.
The others are simple grammar mistakes. One comment in pg_upgrade
referred incorrectly to sequences since a7e5457
.
Author: Justin Pryzby
Discussion: https://postgr.es/m/20221230231257.GI1153@telsasoft.com
Backpatch-through: 11
This commit is contained in:
@ -128,7 +128,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
|
||||
|
||||
<para>
|
||||
In addition, the system must not be running in single-user mode. Since
|
||||
the entire database system is running in single process in this situation,
|
||||
the entire database system is running as a single process in this situation,
|
||||
no background workers will be available.
|
||||
</para>
|
||||
|
||||
|
@ -1001,7 +1001,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
|
||||
constraint. This does not work, however, if any of the partition keys
|
||||
is an expression and the partition does not accept
|
||||
<literal>NULL</literal> values. If attaching a list partition that will
|
||||
not accept <literal>NULL</literal> values, also add
|
||||
not accept <literal>NULL</literal> values, also add a
|
||||
<literal>NOT NULL</literal> constraint to the partition key column,
|
||||
unless it's an expression.
|
||||
</para>
|
||||
@ -1373,7 +1373,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
|
||||
type or an unconstrained domain over the new type, a table rewrite is not
|
||||
needed. However, indexes must always be rebuilt unless the system can
|
||||
verify that the new index would be logically equivalent to the existing
|
||||
one. For example, if the collation for a column has been changed an index
|
||||
one. For example, if the collation for a column has been changed, an index
|
||||
rebuild is always required because the new sort order might be different.
|
||||
However, in the absence of a collation change, a column can be changed
|
||||
from <type>text</type> to <type>varchar</type> (or vice versa) without
|
||||
|
@ -350,7 +350,7 @@ CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceabl
|
||||
<literal>FOR TABLES IN SCHEMA</literal>, rows are always published
|
||||
regardless of the definition of the other expressions.
|
||||
If the subscriber is a <productname>PostgreSQL</productname> version before
|
||||
15 then any row filtering is ignored during the initial data synchronization
|
||||
15, then any row filtering is ignored during the initial data synchronization
|
||||
phase. For this case, the user might want to consider deleting any initially
|
||||
copied data that would be incompatible with subsequent filtering.
|
||||
Because initial data synchronization does not take into account the publication
|
||||
|
@ -935,8 +935,8 @@ BETTER: unrecognized node type: 42
|
||||
<simplesect>
|
||||
<title>Function-Like Macros and Inline Functions</title>
|
||||
<para>
|
||||
Both, macros with arguments and <literal>static inline</literal>
|
||||
functions, may be used. The latter are preferable if there are
|
||||
Both macros with arguments and <literal>static inline</literal>
|
||||
functions may be used. The latter are preferable if there are
|
||||
multiple-evaluation hazards when written as a macro, as e.g., the
|
||||
case with
|
||||
<programlisting>
|
||||
|
Reference in New Issue
Block a user