Re: RFC: replace pg_stat_activity.waiting with something more descriptive

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Vladimir Borodin <root(at)simply(dot)name>, 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>
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Date: 2016-02-24 21:24:05
Message-ID: 56CE1F75.9010208@gmx.net
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Could you enhance the documentation about the difference between "wait
event type name" and "wait event name" (examples?)? This is likely to
be quite confusing for users who are used to just the plain "waiting"
column.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Sewell 2016-02-24 23:06:34 Random note of encouragement
Previous Message Peter Eisentraut 2016-02-24 21:18:10 Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types