On Wed, Apr 18, 2018 at 10:08 AM, Konstantin Knizhnik <k.knizh...@postgrespro.ru> wrote: > And it is very hard not to notice 17-times difference. > Certainly it is true in the assumption that most deadlock timeout expiration > are caused by high workload and contention, and not by real deadlocks. > But it seems to be quite common case.
If I understand this workload correctly, the contention is for the relation extension lock. But I think we're likely to move that out of the heavyweight lock manager altogether in the not-too-distant future, as proposed in https://commitfest.postgresql.org/17/1133/ ? I'd be interested in hearing what happens to performance with that patch applied. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
