Commitf7c566a

committed

Fix a few more redundant calls of GetLatestSnapshot()

Commit2367503 fixed this in RelationFindReplTupleByIndex(), but Imissed two other similar cases.Per report from Ranier Vilela.Discussion:https://www.postgresql.org/message-id/CAEudQArUT1dE45WN87F-Gb7XMy_hW6x1DFd3sqdhhxP-RMDa0Q@mail.gmail.comBackpatch-through: 13

1 parent2367503 commitf7c566aCopy full SHA for f7c566a

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -411,7 +411,7 @@ RelationFindReplTupleSeq(Relation rel, LockTupleMode lockmode,`
`411`	`411`
`412`	`412`	`PushActiveSnapshot(GetLatestSnapshot());`
`413`	`413`
`414`		`-res=table_tuple_lock(rel,&(outslot->tts_tid),GetLatestSnapshot(),`
	`414`	`+res=table_tuple_lock(rel,&(outslot->tts_tid),GetActiveSnapshot(),`
`415`	`415`	`outslot,`
`416`	`416`	`GetCurrentCommandId(false),`
`417`	`417`	`lockmode,`
`@@ -468,7 +468,7 @@ FindConflictTuple(ResultRelInfo resultRelInfo, EState estate,`
`468`	`468`
`469`	`469`	`PushActiveSnapshot(GetLatestSnapshot());`
`470`	`470`
`471`		`-res=table_tuple_lock(rel,&conflictTid,GetLatestSnapshot(),`
	`471`	`+res=table_tuple_lock(rel,&conflictTid,GetActiveSnapshot(),`
`472`	`472`	`*conflictslot,`
`473`	`473`	`GetCurrentCommandId(false),`
`474`	`474`	`LockTupleShare,`

Comments

(0)