Skip to content

Commit c772dfe

Browse files
committed
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
1 parent c6e75e4 commit c772dfe

File tree

16 files changed

+22
-23
lines changed

16 files changed

+22
-23
lines changed

.cirrus.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ env:
1111
CONTAINER_REPO: us-docker.pkg.dev/${GCP_PROJECT}/ci
1212

1313
# The lower depth accelerates git clone. Use a bit of depth so that
14-
# concurrent tasks and retrying older jobs has a chance of working.
14+
# concurrent tasks and retrying older jobs have a chance of working.
1515
CIRRUS_CLONE_DEPTH: 500
1616
# Useful to be able to analyse what in a script takes long
1717
CIRRUS_LOG_TIMESTAMP: true
@@ -66,7 +66,7 @@ task:
6666
6767
ccache_cache:
6868
folder: $CCACHE_DIR
69-
# Workaround around performance issues due to 32KB block size
69+
# Work around performance issues due to 32KB block size
7070
repartition_script: src/tools/ci/gcp_freebsd_repartition.sh
7171
create_user_script: |
7272
pw useradd postgres

doc/src/sgml/parallel.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
128128

129129
<para>
130130
In addition, the system must not be running in single-user mode. Since
131-
the entire database system is running in single process in this situation,
131+
the entire database system is running as a single process in this situation,
132132
no background workers will be available.
133133
</para>
134134

doc/src/sgml/ref/alter_table.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1001,7 +1001,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
10011001
constraint. This does not work, however, if any of the partition keys
10021002
is an expression and the partition does not accept
10031003
<literal>NULL</literal> values. If attaching a list partition that will
1004-
not accept <literal>NULL</literal> values, also add
1004+
not accept <literal>NULL</literal> values, also add a
10051005
<literal>NOT NULL</literal> constraint to the partition key column,
10061006
unless it's an expression.
10071007
</para>
@@ -1373,7 +1373,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
13731373
type or an unconstrained domain over the new type, a table rewrite is not
13741374
needed. However, indexes must always be rebuilt unless the system can
13751375
verify that the new index would be logically equivalent to the existing
1376-
one. For example, if the collation for a column has been changed an index
1376+
one. For example, if the collation for a column has been changed, an index
13771377
rebuild is always required because the new sort order might be different.
13781378
However, in the absence of a collation change, a column can be changed
13791379
from <type>text</type> to <type>varchar</type> (or vice versa) without

doc/src/sgml/ref/create_subscription.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -350,7 +350,7 @@ CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceabl
350350
<literal>FOR TABLES IN SCHEMA</literal>, rows are always published
351351
regardless of the definition of the other expressions.
352352
If the subscriber is a <productname>PostgreSQL</productname> version before
353-
15 then any row filtering is ignored during the initial data synchronization
353+
15, then any row filtering is ignored during the initial data synchronization
354354
phase. For this case, the user might want to consider deleting any initially
355355
copied data that would be incompatible with subsequent filtering.
356356
Because initial data synchronization does not take into account the publication

doc/src/sgml/sources.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -935,8 +935,8 @@ BETTER: unrecognized node type: 42
935935
<simplesect>
936936
<title>Function-Like Macros and Inline Functions</title>
937937
<para>
938-
Both, macros with arguments and <literal>static inline</literal>
939-
functions, may be used. The latter are preferable if there are
938+
Both macros with arguments and <literal>static inline</literal>
939+
functions may be used. The latter are preferable if there are
940940
multiple-evaluation hazards when written as a macro, as e.g., the
941941
case with
942942
<programlisting>

src/backend/access/common/bufmask.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ mask_unused_space(Page page)
7878
if (pd_lower > pd_upper || pd_special < pd_upper ||
7979
pd_lower < SizeOfPageHeaderData || pd_special > BLCKSZ)
8080
{
81-
elog(ERROR, "invalid page pd_lower %u pd_upper %u pd_special %u\n",
81+
elog(ERROR, "invalid page pd_lower %u pd_upper %u pd_special %u",
8282
pd_lower, pd_upper, pd_special);
8383
}
8484

src/backend/access/spgist/spgutils.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1301,7 +1301,7 @@ spgproperty(Oid index_oid, int attno,
13011301
/*
13021302
* Currently, SP-GiST distance-ordered scans require that there be a
13031303
* distance operator in the opclass with the default types. So we assume
1304-
* that if such a operator exists, then there's a reason for it.
1304+
* that if such an operator exists, then there's a reason for it.
13051305
*/
13061306

13071307
/* First we need to know the column's opclass. */

src/backend/jit/llvm/llvmjit.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -816,7 +816,7 @@ llvm_session_initialize(void)
816816

817817
if (LLVMGetTargetFromTriple(llvm_triple, &llvm_targetref, &error) != 0)
818818
{
819-
elog(FATAL, "failed to query triple %s\n", error);
819+
elog(FATAL, "failed to query triple %s", error);
820820
}
821821

822822
/*

src/backend/optimizer/util/tlist.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -865,7 +865,7 @@ apply_pathtarget_labeling_to_tlist(List *tlist, PathTarget *target)
865865
*
866866
* The outputs of this function are two parallel lists, one a list of
867867
* PathTargets and the other an integer list of bool flags indicating
868-
* whether the corresponding PathTarget contains any evaluatable SRFs.
868+
* whether the corresponding PathTarget contains any evaluable SRFs.
869869
* The lists are given in the order they'd need to be evaluated in, with
870870
* the "lowest" PathTarget first. So the last list entry is always the
871871
* originally given PathTarget, and any entries before it indicate evaluation

src/backend/utils/adt/ruleutils.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11416,7 +11416,7 @@ get_opclass_name(Oid opclass, Oid actual_datatype,
1141611416

1141711417
/*
1141811418
* generate_opclass_name
11419-
* Compute the name to display for a opclass specified by OID
11419+
* Compute the name to display for an opclass specified by OID
1142011420
*
1142111421
* The result includes all necessary quoting and schema-prefixing.
1142211422
*/

0 commit comments

Comments
 (0)