| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Addition of authenticated ID to pg_stat_activity |
| Date: | 2021-04-27 18:24:57 |
| Message-ID: | 20210427182457.d5ptpl4kk5axvhyi@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2021-04-27 12:40:29 -0400, Stephen Frost wrote:
> So, what fields are people really looking at when querying
> pg_stat_activity interactively? User, database, pid, last query,
> transaction start, query start, state, wait event info, maybe backend
> xmin/xid? I doubt most people looking at pg_stat_activity interactively
> actually care about the non-user backends (autovacuum, et al).
Not representative, but I personally am about as often interested in one
of the non-connection processes as the connection
ones. E.g. investigating what is autovacuum's bottleneck, are
checkpointer / wal writer / bgwriter io bound or keeping up, etc.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-04-27 20:21:19 | Release 14 Beta 1 |
| Previous Message | Andres Freund | 2021-04-27 18:22:36 | Re: Performance degradation of REFRESH MATERIALIZED VIEW |