Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit1c7a0b3

Browse files
committed
Add missing break out seqscan loop in logical replication
When replica identity is FULL (an admittedly unusual case), the loopthat searches for tuples in execReplication.c didn't stop scanning thetable when once a matching tuple was found. Add the missing 'break'.Note slight behavior change: we now return the first matching tuplerather than the last one. They are supposed to be indistinguishableanyway, so this shouldn't matter.Author: Konstantin KnizhnikDiscussion:https://postgr.es/m/379743f6-ae91-b866-f7a2-5624e6d2b0a4@postgrespro.ru
1 parentf1f10a1 commit1c7a0b3

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

‎src/backend/executor/execReplication.c

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -327,6 +327,9 @@ RelationFindReplTupleSeq(Relation rel, LockTupleMode lockmode,
327327
XactLockTableWait(xwait,NULL,NULL,XLTW_None);
328328
gotoretry;
329329
}
330+
331+
/* Found our tuple and it's not locked */
332+
break;
330333
}
331334

332335
/* Found tuple, try to lock it in the lockmode. */

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp