Search Postgresql Archives
Re: relationship of backend_start, query_start, state_change
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: relationship of backend_start, query_start, state_change
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Thu, 23 Apr 2020 10:46:44 -0600
Cc
: PostgreSQL General <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to
: <CAAYSSjOYNAnjMD_sEp-GOivTezWEbGZFOVeW2MG_q-E6h86q=Q@mail.gmail.com>
References
: <CAAYSSjOYNAnjMD_sEp-GOivTezWEbGZFOVeW2MG_q-E6h86q=Q@mail.gmail.com>
If you use a connection pooler, this would likely be expected behavior since the connection is getting reused many times. Else, some app is connected and not closing their connection between queries. At least they aren't idle in transaction though.
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
References
:
relationship of backend_start, query_start, state_change
From:
Si Chen
Prev by Date:
Re: Reg: Help to understand the source code
Next by Date:
Re: relationship of backend_start, query_start, state_change
Previous by thread:
relationship of backend_start, query_start, state_change
Next by thread:
Re: relationship of backend_start, query_start, state_change
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
