Hi, Currently RelationFindReplTupleByIndex(), RelationFindReplTupleSeq() lock the found tuple. I don't quite get what that achieves - why isn't dealing with concurrency in the table_update/delete calls at the callsites sufficient? As far as I can tell there's no meaningful concurrency handling in the heap_lock_tuple() paths, so it's not like we follow update chains or anything. As far as I can tell this just nearly doubles the number of WAL records when replaying updates/deletes?
Greetings, Andres Freund
