| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Locks analyze |
| Date: | 2023-10-13 11:59:35 |
| Message-ID: | f7d8b0bc16be17cc38d97ce90ad9060f7fb9d8f3.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2023-10-13 at 15:09 +0530, Rajesh Kumar wrote:
> How do I identify a session that is blocked?
See "wait_event_type" in "pg_stat_activity" (or see "pg_locks").
> Can blocking sessions increase idle sessions?
Only within certain limits, unless your applicaton is doing something wrong.
> I see something like waitdurarion in pg_locks..is that helpful anyway?
Yes, that means that the session has been waiting for the lock for a while.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Christophe Boggio | 2023-10-13 13:06:57 | One PG process eating more than 40GB of RAM and getting killed by OOM |
| Previous Message | Rajesh Kumar | 2023-10-13 09:39:18 | Re: Locks analyze |