Skip to content

Commit 6d3b489

Browse files
michaelpqpull[bot]
authored andcommitted
Fix various typos in code and tests
Most of these are recent, and the documentation portions are new as of v16 so there is no need for a backpatch. Author: Justin Pryzby Discussion: https://postgr.es/m/20230208155644.GM1653@telsasoft.com
1 parent 0b71fb4 commit 6d3b489

File tree

20 files changed

+24
-23
lines changed

20 files changed

+24
-23
lines changed

contrib/postgres_fdw/deparse.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2412,7 +2412,7 @@ deparseAnalyzeInfoSql(StringInfo buf, Relation rel)
24122412
*
24132413
* We could also do "ORDER BY random() LIMIT x", which would always pick
24142414
* the expected number of rows, but it requires sorting so it may be much
2415-
* more expensive (particularly on large tables, which is what what the
2415+
* more expensive (particularly on large tables, which is what the
24162416
* remote sampling is meant to improve).
24172417
*/
24182418
void

doc/src/sgml/config.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -718,7 +718,7 @@ include_dir 'conf.d'
718718
<para>
719719
Determines the number of connection <quote>slots</quote> that are
720720
reserved for connections by roles with privileges of the
721-
<link linkend="predefined-roles-table"><literal>pg_used_reserved_connections</literal></link>
721+
<link linkend="predefined-roles-table"><literal>pg_use_reserved_connections</literal></link>
722722
role. Whenever the number of free connection slots is greater than
723723
<xref linkend="guc-superuser-reserved-connections"/> but less than or
724724
equal to the sum of <varname>superuser_reserved_connections</varname>

doc/src/sgml/ref/create_database.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ CREATE DATABASE <replaceable class="parameter">name</replaceable>
8989
The role name of the user who will own the new database,
9090
or <literal>DEFAULT</literal> to use the default (namely, the
9191
user executing the command). To create a database owned by another
92-
role, you must must be able to <literal>SET ROLE</literal> to that
92+
role, you must be able to <literal>SET ROLE</literal> to that
9393
role.
9494
</para>
9595
</listitem>

doc/src/sgml/ref/create_schema.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ CREATE SCHEMA IF NOT EXISTS AUTHORIZATION <replaceable class="parameter">role_sp
8989
<para>
9090
The role name of the user who will own the new schema. If omitted,
9191
defaults to the user executing the command. To create a schema
92-
owned by another role, you must must be able to
92+
owned by another role, you must be able to
9393
<literal>SET ROLE</literal> to that role.
9494
</para>
9595
</listitem>

src/backend/commands/dbcommands.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3090,7 +3090,7 @@ dbase_redo(XLogReaderState *record)
30903090

30913091
/*
30923092
* There's a case where the copy source directory is missing for the
3093-
* same reason above. Create the emtpy source directory so that
3093+
* same reason above. Create the empty source directory so that
30943094
* copydir below doesn't fail. The directory will be dropped soon by
30953095
* recovery.
30963096
*/

src/backend/executor/execMain.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ ExecutorStart(QueryDesc *queryDesc, int eflags)
134134
/*
135135
* In some cases (e.g. an EXECUTE statement) a query execution will skip
136136
* parse analysis, which means that the query_id won't be reported. Note
137-
* that it's harmless to report the query_id multiple time, as the call
137+
* that it's harmless to report the query_id multiple times, as the call
138138
* will be ignored if the top level query_id has already been reported.
139139
*/
140140
pgstat_report_query_id(queryDesc->plannedstmt->queryId, false);

src/backend/jit/llvm/llvmjit_inline.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -753,7 +753,7 @@ function_inlinable(llvm::Function &F,
753753
/* import referenced function itself */
754754
importVars.insert(referencedFunction->getName());
755755

756-
/* import referenced function and its dependants */
756+
/* import referenced function and its dependents */
757757
for (auto& recImportVar : recImportVars)
758758
importVars.insert(recImportVar.first());
759759
}

src/backend/replication/logical/snapbuild.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1816,7 +1816,7 @@ SnapBuildSerialize(SnapBuild *builder, XLogRecPtr lsn)
18161816
fsync_fname("pg_logical/snapshots", true);
18171817

18181818
/*
1819-
* Now there's no way we can loose the dumped state anymore, remember this
1819+
* Now there's no way we can lose the dumped state anymore, remember this
18201820
* as a serialization point.
18211821
*/
18221822
builder->last_serialized_snapshot = lsn;

src/backend/replication/walsender.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2050,9 +2050,9 @@ PhysicalConfirmReceivedLocation(XLogRecPtr lsn)
20502050

20512051
/*
20522052
* One could argue that the slot should be saved to disk now, but that'd
2053-
* be energy wasted - the worst lost information can do here is give us
2054-
* wrong information in a statistics view - we'll just potentially be more
2055-
* conservative in removing files.
2053+
* be energy wasted - the worst thing lost information could cause here is
2054+
* to give wrong information in a statistics view - we'll just potentially
2055+
* be more conservative in removing files.
20562056
*/
20572057
}
20582058

src/bin/pg_basebackup/pg_basebackup.c

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2015,8 +2015,9 @@ BaseBackup(char *compression_algorithm, char *compression_detail,
20152015
* If we write the data out to a tar file, it will be named
20162016
* base.tar if it's the main data directory or <tablespaceoid>.tar
20172017
* if it's for another tablespace. CreateBackupStreamer() will
2018-
* arrange to add .gz to the archive name if pg_basebackup is
2019-
* performing compression.
2018+
* arrange to add an extension to the archive name if
2019+
* pg_basebackup is performing compression, depending on the
2020+
* compression type.
20202021
*/
20212022
if (PQgetisnull(res, i, 0))
20222023
{

0 commit comments

Comments
 (0)