git.postgresql.org Git - postgresql.git/commitdiff

git projects / postgresql.git / commitdiff

author Masahiko Sawada <msawada@postgresql.org>

2025年8月16日 08:11:40 +0000 (01:11 -0700)

committer Masahiko Sawada <msawada@postgresql.org>

2025年8月16日 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 patch | blob | blame | history

src/backend/replication/logical/worker.c patch | blob | blame | history

diff --git a/src/backend/executor/execReplication.c b/src/backend/executor/execReplication.c

index 68184f5d671e2c1affd0119df747ddd1e9f1b5cc..da0cbf41d6f88014fa8025422e73b36a27fa8cd3 100644 (file)

--- a/src/backend/executor/execReplication.c

+++ b/src/backend/executor/execReplication.c

@@ -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,

diff --git a/src/backend/replication/logical/worker.c b/src/backend/replication/logical/worker.c

index 59b6ae7719ab1ac83b1452da19523a94825f54f8..8e34387345495b3d5cde7a359e45f1bb62e3968b 100644 (file)

--- a/src/backend/replication/logical/worker.c

+++ b/src/backend/replication/logical/worker.c

@@ -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,

This is the main PostgreSQL git repository.

RSS Atom