Possible optimization of heap_lock_tuple()
Started by Antonin Houskaalmost 5 years ago1 messageshackers
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