| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: exposing wait events for non-backends (was: Tracking wait event for latches) |
| Date: | 2016-12-12 16:45:00 |
| Message-ID: | CA+TgmoZcdgTf_x3cMJ09EzTmMiAeceECCTxc44R2sf67gBx_wA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 12, 2016 at 11:19 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> So, one of the problems in this patch as committed is that for any
> process that doesn't show up in pg_stat_activity, there's no way to
> see the wait event information. That sucks. I think there are
> basically two ways to fix this:
>
> 1. Show all processes that have a PGPROC in pg_stat_activity,
> including auxiliary processes and whatnot, and use some new field in
> pg_stat_activity to indicate the process type.
>
> 2. Add a second view, say pg_stat_system_activity, to show the
> processes that don't appear in pg_stat_activity. A bunch of columns
> could likely be omitted, but there would be some duplication, too.
>
> Preferences?
And now I'm noticing that Michael Paquier previously started a thread
on this problem which I failed to note before starting this one:
http://postgr.es/m/CAB7nPqSYN05rGsYCTahxTz+2hBikh7=m+hr2JTXaZv_Ei=qJAg@mail.gmail.com
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-12-12 16:52:30 | Re: Nested Wait Events? |
| Previous Message | David G. Johnston | 2016-12-12 16:34:47 | Re: exposing wait events for non-backends (was: Tracking wait event for latches) |