Re: proposal: add 'waiting for replication' to pg_stat_activity.state - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: proposal: add 'waiting for replication' to pg_stat_activity.state
Date
Msg-id 565F9BB9.1060003@gmx.net
Whole thread Raw
In response to Re: proposal: add 'waiting for replication' to pg_stat_activity.state  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: proposal: add 'waiting for replication' to pg_stat_activity.state  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 12/2/15 7:00 PM, Craig Ringer wrote:
> I notice that you don't set the 'waiting' flag.  'waiting' is presently
> documented as:
> 
>        <entry>True if this backend is currently waiting on a lock</entry>
> 
> ... but I'm inclined to just widen its definition and set it here, since
> we most certainly are waiting, and the column isn't named
> 'waiting_on_a_lock'. It shouldn't upset various canned lock monitoring
> queries people have since they generally do an inner join on pg_locks
> anyway.

I'm not so sure about that assumption.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Removing Functionally Dependent GROUP BY Columns
Next
From: Michael Paquier
Date:
Subject: Re: psql: add \pset true/false