From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Subject: | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |
Date: | 2015-11-14 14:45:17 |
Message-ID: | CAMsr+YG3pOm1OiALZQ0DkiA6647cUsWcRExMcHucfWPwYMAMng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 14 November 2015 at 15:50, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> One thing that occurred to me in this context is that if we store the wait
> event information in PGPROC, then can we think of providing the info
> about wait events in a separate view pg_stat_waits (or pg_stat_wait_info or
> any other better name) where we can display wait information about
> all-processes rather than only backends?
>
Sounds good to me. Consider a logical decoding plugin in a walsender for
example.
> This will avoid the confusion
> about breaking the backward compatibility for the current 'waiting' column
> in pg_stat_activity.
>
I'm about -10^7 on changing the 'waiting' column. I am still seeing
confused users from the 'procpid' to 'pid' renaming. If more info is
needed, add a column with more detail or, as you suggest here, use a new
view.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-11-14 16:13:39 | Re: Inaccurate results from numeric ln(), log(), exp() and pow() |
Previous Message | Craig Ringer | 2015-11-14 14:41:25 | Re: eXtensible Transaction Manager API |