Re: Locks analyze - Mailing list pgsql-admin

From Rajesh Kumar
Subject Re: Locks analyze
Date
Msg-id CAJk5AtZBhKzgu9KOMDxyC7FxTsULS2hWRJ=Zod+2kzmL+KEhnw@mail.gmail.com
Whole thread Raw
In response to Re: Locks analyze  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Locks analyze
Re: Locks analyze
List pgsql-admin
How do I identify a session that is blocked? 

Can blocking sessions increase idle sessions?

I see something like waitdurarion in pg_locks..is that helpful anyway?

I am often facing idle connection spike. That is why I am checking all these.

On Fri, 13 Oct, 2023, 11:32 AM Laurenz Albe, <laurenz.albe@cybertec.at> wrote:
On Fri, 2023-10-13 at 05:16 +0530, Rajesh Kumar wrote:
> How do I analyze locks and resolve it. Is there only one query that helps?
> This lock issue leading to high connections it seems.

Once you have identified a session that is blocked, get its process ID
from pg_stat_activity and SELECT pg_blocking_pids(12345);
with that process number as argument.

Then you get all the other sessions that block that session.

Yours,
Laurenz Albe

pgsql-admin by date:

Previous
From: Rajesh Kumar
Date:
Subject: Re: Automation
Next
From: Laurenz Albe
Date:
Subject: Re: Locks analyze