| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Edwin UY <edwin(dot)uy(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to check if session is a hung thread/session |
| Date: | 2024-11-11 04:45:38 |
| Message-ID: | 216310.1731300338@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Edwin UY <edwin(dot)uy(at)gmail(dot)com> writes:
> I thought it could be the backend has sent something back to the client but
> it never received it and it just kept on doing the same at some intervals.
Your pg_stat_activity output shows the backend is idle, meaning it's
waiting for a client command. While the session has been around for
days, we can see the last client command was about 47 minutes ago,
from your "now() - pg_stat_activity.query_start AS duration" column.
I see no reason to think there is anything interesting here at all,
except for a client that is sitting doing nothing for long periods.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | p sn | 2024-11-11 06:02:44 | Inquiry on Setting Up Automatic Failover with Stream Replication |
| Previous Message | Edwin UY | 2024-11-11 04:13:17 | Re: How to check if session is a hung thread/session |