Re: Lock contention high

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Ashkil Dighin <ashkildighin76(at)gmail(dot)com>
Cc: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Lock contention high
Date: 2021-10-14 06:42:57
Message-ID: 8b8d8aa90acbe9118c0fc1e598f912ca7cfa70db.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, 2021-10-14 at 11:33 +0530, Ashkil Dighin wrote:
> Captured the concurrent session with Netsat and pg-stat-actvity. Is the procedure the right way to capture concurrent sesssions in postgresql?
>
> Select pg_stat_activity

[some two dozen sessions]

That doesn't look like you would get into trouble just from the
sheer number of sessions, so it must be something else.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ashkil Dighin 2021-10-14 06:45:19 Re: Lock contention high
Previous Message Ashkil Dighin 2021-10-14 06:03:58 Re: Lock contention high