Re: Add connection active, idle time to pg_stat_activity

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>

To: kuntalghosh.2007@gmail.com

Cc: rafia.pghackers@gmail.com, pgsql-hackers@lists.postgresql.org

Date: 2022-01-28T05:40:24Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Remove unstable pg_amcheck tests.
- cd3f429d9565 15.0 cited

At Mon, 29 Nov 2021 20:34:14 +0530, Kuntal Ghosh <kuntalghosh.2007@gmail.com> wrote in 
> active_time. But, I'm wondering why you need to distinguish between
> idle and idle in transactions - what's the usage? Either the backend
> is doing some work or it sits idle. Another useful information would

I believe many people suffer from mysterious long idle in
transactions, which harm server performance many ways.  In many cases
transactions with unexpectedly long idle time is an omen or a cause of
trouble.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center