On Fri, Apr 20, 2018 at 12:14 PM, Konstantin Knizhnik <k.knizh...@postgrespro.ru> wrote: > With the extension lock patch performance in increased to 1146 TPS. > So it is much better than with vanilla postgres and about 40% better than > with deadlock patch (1146 vs. 719 TPS).
Cool, that's good to know. > So definitely elimination heavy weight relation extension lock is good idea > which eliminates the need for my deadlock patch ... but only in this insert > test. > As I have mentioned at the beginning of this thread the same problem with > deadlock detection timeout expiration we have with YSCB benchmark with zipf > distribution. > Here the source of contention are tuple locks. And as far as I understand > from the discussion in the mentioned thread, it is not possible to eliminate > heavy weight tuple locks. Right, that variant would have to be solved in some other way. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
