| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Si Chen <sichen(at)opensourcestrategies(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: relationship of backend_start, query_start, state_change |
| Date: | 2020-04-23 16:55:06 |
| Message-ID: | CAKFQuwbPCuMmk2FUwOPiU6fvh_nJ=onO-ayCFTiiXvRmjCfLUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 23, 2020 at 9:37 AM Si Chen <sichen(at)opensourcestrategies(dot)com>
wrote:
> Hello,
>
> I'm looking at my pg_stat_activity and trying to figure out what is
> causing some of these processes. I'm using this query:
>
> SELECT pid, wait_event, state_change, backend_start, xact_start,
> query_start, state_change - query_start, query from pg_stat_activity where
> datname= 'my_database' and state in ('idle', 'idle in transaction', 'idle
> in transaction (aborted)', 'disabled');
>
>
Including the "state" field should clear things up considerably.
https://www.postgresql.org/docs/current/monitoring-stats.html#PG-STAT-ACTIVITY-VIEW
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Olivier Gautherot | 2020-04-23 16:58:36 | Re: relationship of backend_start, query_start, state_change |
| Previous Message | Olivier Gautherot | 2020-04-23 16:54:53 | Re: relationship of backend_start, query_start, state_change |