Thread: Possible optimization of heap_lock_tuple()

It seems that a concurrent UPDATE can restart heap_lock_tuple() even if it's
not necessary. Is the attached proposal correct and worth applying?

-- 
Antonin Houska
Web: https://www.cybertec-postgresql.com