Content-Type: multipart/alternative;
 boundary="------------vSFVQwaHeVFmmRWNdAgDNwQF"
Message-ID: <938bdd7b-9a0d-1675-2c6c-ed1420f42b32@gmail.com>
Date: Tue, 12 Oct 2021 11:37:20 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.1.0
Subject: Re: Lock contention high
Content-Language: en-US
To: pgsql-performance@lists.postgresql.org
References: 
 <CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com>
From: Mladen Gogala <gogala.mladen@gmail.com>
In-Reply-To: 
 <CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/938bdd7b-9a0d-1675-2c6c-ed1420f42b32%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------vSFVQwaHeVFmmRWNdAgDNwQF
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


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

--------------vSFVQwaHeVFmmRWNdAgDNwQF
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 10/12/21 03:35, Ashkil Dighin wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com"><font
        color="#000000">1.Is there a way to tune the lock contention ?</font></blockquote>
    <p>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.<br>
    </p>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
<a class="moz-txt-link-freetext" href="https://dbwhisperer.wordpress.com">https://dbwhisperer.wordpress.com</a>
</pre>
  </body>
</html>
--------------vSFVQwaHeVFmmRWNdAgDNwQF--