Closed NickyMateev closed 4 years ago
Concurrent update/read operations were susceptible to sharelock deadlocking.
Reference about locking: https://www.postgresql.org/docs/9.4/explicit-locking.html
Coverage decreased (-0.2%) to 86.772% when pulling ad28d3aaef8aa07391130600f91e3a41bdab1905 on fix-sharelocck-deadlock into f37bab8e388081d057b186a4a13389d00496ffca on master.
Fix ShareLock deadlock
Motivation
Concurrent update/read operations were susceptible to sharelock deadlocking.
Reference about locking: https://www.postgresql.org/docs/9.4/explicit-locking.html
Pull Request status