Re: relationship of backend_start, query_start, state_change
От | David G. Johnston |
---|---|
Тема | Re: relationship of backend_start, query_start, state_change |
Дата | |
Msg-id | CAKFQuwbPCuMmk2FUwOPiU6fvh_nJ=onO-ayCFTiiXvRmjCfLUA@mail.gmail.com обсуждение исходный текст |
Ответ на | relationship of backend_start, query_start, state_change (Si Chen <sichen@opensourcestrategies.com>) |
Ответы |
Re: relationship of backend_start, query_start, state_change
Re: relationship of backend_start, query_start, state_change |
Список | pgsql-general |
On Thu, Apr 23, 2020 at 9:37 AM Si Chen <sichen@opensourcestrategies.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.
David J.
В списке pgsql-general по дате отправления: