]> git.ipfire.org Git - thirdparty/postgresql.git/commitdiff
Fix typos in comments.
authorMasahiko Sawada <msawada@postgresql.org>
Sat, 16 Aug 2025 08:11:40 +0000 (01:11 -0700)
committerMasahiko Sawada <msawada@postgresql.org>
Sat, 16 Aug 2025 08:11:40 +0000 (01:11 -0700)
Oversight in commit fd5a1a0c3e56.

Author: Tender Wang <tndrwang@gmail.com>
Discussion: https://postgr.es/m/CAHewXNmTT3M_w4NngG=6G3mdT3iJ6DdncTqV9YnGXBPHW8XYtA@mail.gmail.com

src/backend/executor/execReplication.c
src/backend/replication/logical/worker.c

index 68184f5d671e2c1affd0119df747ddd1e9f1b5cc..da0cbf41d6f88014fa8025422e73b36a27fa8cd3 100644 (file)
@@ -582,7 +582,7 @@ RelationFindDeletedTupleInfoSeq(Relation rel, TupleTableSlot *searchslot,
         * IsIndexUsableForFindingDeletedTuple), a full table scan becomes
         * necessary. In such cases, comparing the entire tuple is not required,
         * since the remote tuple might not include all column values. Instead,
-        * the indexed columns alone are suffcient to identify the target tuple
+        * the indexed columns alone are sufficient to identify the target tuple
         * (see logicalrep_rel_mark_updatable).
         */
        indexbitmap = RelationGetIndexAttrBitmap(rel,
index 59b6ae7719ab1ac83b1452da19523a94825f54f8..8e34387345495b3d5cde7a359e45f1bb62e3968b 100644 (file)
@@ -2923,7 +2923,7 @@ apply_handle_update_internal(ApplyExecutionData *edata,
 
                /*
                 * Detecting whether the tuple was recently deleted or never existed
-                * is crucial to avoid misleading the user during confict handling.
+                * is crucial to avoid misleading the user during conflict handling.
                 */
                if (FindDeletedTupleInLocalRel(localrel, localindexoid, remoteslot,
                                                                           &conflicttuple.xmin,
@@ -3392,7 +3392,7 @@ apply_handle_tuple_routing(ApplyExecutionData *edata,
                                        /*
                                         * Detecting whether the tuple was recently deleted or
                                         * never existed is crucial to avoid misleading the user
-                                        * during confict handling.
+                                        * during conflict handling.
                                         */
                                        if (FindDeletedTupleInLocalRel(partrel,
                                                                                                   part_entry->localindexoid,