aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/cache
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2022-04-11 20:49:41 +1200
committerDavid Rowley <drowley@postgresql.org>2022-04-11 20:49:41 +1200
commitb0e5f02ddc836499bdcf093df52e4c342dda5891 (patch)
tree2211dfcfabd04e9ecd5b32b1b5fd3e97c817bc91 /src/backend/utils/cache
parentbba3c35b29d07a27bbf5dd0d7d5e7c7592e02f81 (diff)
downloadpostgresql-b0e5f02ddc836499bdcf093df52e4c342dda5891.tar.gz
postgresql-b0e5f02ddc836499bdcf093df52e4c342dda5891.zip
Fix various typos and spelling mistakes in code comments
Author: Justin Pryzby Discussion: https://postgr.es/m/20220411020336.GB26620@telsasoft.com
Diffstat (limited to 'src/backend/utils/cache')
-rw-r--r--src/backend/utils/cache/relmapper.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/utils/cache/relmapper.c b/src/backend/utils/cache/relmapper.c
index dee3387d026..75a3aedc5af 100644
--- a/src/backend/utils/cache/relmapper.c
+++ b/src/backend/utils/cache/relmapper.c
@@ -1044,7 +1044,7 @@ perform_relmap_update(bool shared, const RelMapFile *updates)
(shared ? "global" : DatabasePath));
/*
- * We succesfully wrote the updated file, so it's now safe to rely on the
+ * We successfully wrote the updated file, so it's now safe to rely on the
* new values in this process, too.
*/
if (shared)
@@ -1093,7 +1093,7 @@ relmap_redo(XLogReaderState *record)
* an existing database as we do for creating a new database. In
* the latter case, taking the relmap log and sending sinval messages
* is unnecessary, but harmless. If we wanted to avoid it, we could
- * add a flag to the WAL record to indicate which opration is being
+ * add a flag to the WAL record to indicate which operation is being
* performed.
*/
LWLockAcquire(RelationMappingLock, LW_EXCLUSIVE);