pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Ashkil Dighin <ashkildighin76@gmail.com>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: Lock contention high
Date: Thu, 14 Oct 2021 08:42:57 +0200
Message-ID: <8b8d8aa90acbe9118c0fc1e598f912ca7cfa70db.camel@cybertec.at> (raw)
In-Reply-To: <CAH6zzqBjx73nB-MtU6N7BZDtpT_gg_1LhzGvm5G5PaORgp6Kyg@mail.gmail.com>
References: <CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com>
	<51498581960e2ebdc210907d9e8f9b168a068aad.camel@cybertec.at>
	<CAH6zzqBjx73nB-MtU6N7BZDtpT_gg_1LhzGvm5G5PaORgp6Kyg@mail.gmail.com>

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






view thread (26+ messages)  latest in thread

Message-ID: <8b8d8aa90acbe9118c0fc1e598f912ca7cfa70db.camel@cybertec.at>
Permalink:  ../8b8d8aa90acbe9118c0fc1e598f912ca7cfa70db.camel@cybertec.at/
Also on:    postgresql.org/message-id/8b8d8aa90acbe9118c0fc1e598f912ca7cfa70db.camel@cybertec.at

 · 

reply
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: laurenz.albe@cybertec.at, ashkildighin76@gmail.com, pgsql-performance@lists.postgresql.org
  Subject: Re: Lock contention high
  In-Reply-To: <8b8d8aa90acbe9118c0fc1e598f912ca7cfa70db.camel@cybertec.at>

* 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