Re: relationship of backend_start, query_start, state_change
От | Olivier Gautherot |
---|---|
Тема | Re: relationship of backend_start, query_start, state_change |
Дата | |
Msg-id | CAJ7S9TXQyvq56wW4ttSHHKb+9wLmBAbr=r8WbFw9up-MmR5JHQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: relationship of backend_start, query_start, state_change ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: relationship of backend_start, query_start, state_change
|
Список | pgsql-general |
Hi David,
On Thu, Apr 23, 2020 at 6:55 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
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.
The transactions are idle, they are filtered in the WHERE statement.
--
Olivier Gautherot
В списке pgsql-general по дате отправления: