From: Mladen Gogala <gogala.mladen@gmail.com>
To: pgsql-performance@lists.postgresql.org
Subject: Re: Lock contention high
Date: Tue, 12 Oct 2021 11:37:20 -0400
Message-ID: <938bdd7b-9a0d-1675-2c6c-ed1420f42b32@gmail.com> (raw)
In-Reply-To: <CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com>
References: <CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com>
On 10/12/21 03:35, Ashkil Dighin wrote:
> 1.Is there a way to tune the lock contention ?
Lock contention is usually an application issue. Application processes
are stepping on each other's toes. I have never seen a situation where
the database would be slow with managing locks. Postgres uses an
in-memory queue manager which is, generally speaking, very fast.
Applications usually do stupid things. I've seen GUI doing "SELECT FOR
UPDATE". And then the operator decided to have lunch. I'll leave the
rest to your imagination.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gogala.mladen@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Lock contention high
In-Reply-To: <938bdd7b-9a0d-1675-2c6c-ed1420f42b32@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox