Re: proposal: add 'waiting for replication' to pg_stat_activity.state

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>, Julian Schauder <julian(dot)schauder(at)credativ(dot)de>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: add 'waiting for replication' to pg_stat_activity.state
Date: 2015-12-03 01:32:41
Message-ID: 565F9BB9.1060003@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-12-03 01:41:11 Re: psql: add \pset true/false
Previous Message Peter Eisentraut 2015-12-03 01:28:45 Re: Removing Functionally Dependent GROUP BY Columns