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

From Alvaro Herrera
Subject Re: proposal: add 'waiting for replication' to pg_stat_activity.state
Date
Msg-id 20160118174318.GA81321@alvherre.pgsql
Whole thread Raw
In response to Re: proposal: add 'waiting for replication' to pg_stat_activity.state  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund wrote:
> On December 4, 2015 9:48:55 AM GMT+01:00, Craig Ringer <craig@2ndquadrant.com> wrote:
> >On 3 December 2015 at 22:58, Amit Kapila <amit.kapila16@gmail.com>
> >wrote:
> >
> >> On Thu, Dec 3, 2015 at 9:02 AM, Craig Ringer <craig@2ndquadrant.com>
> >> wrote:
> 
> >http://www.postgresql.org/message-id/CAA4eK1+=5Ex8-5NRr3u94=_t2p65v0kcjZ5rXddVmkx=LwAJ+w@mail.gmail.com
> >>
> >Good point. I'm not sure this shouldn't set 'waiting' anyway, though.
> 
> No. Waiting corresponds to pg locks -setting it to true for other things would be even more confusing...

Robert's opinion elsewhere is relevant for this patch, and contradicts
Andres' opinion here:
http://www.postgresql.org/message-id/CA+Tgmoaj+EPoO9qobvFH18F5kJg2tAEXhQ8_-VayWHUr-ZATMw@mail.gmail.com

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Atri Sharma
Date:
Subject: Re: 2016-01 Commitfest
Next
From: Bruce Momjian
Date:
Subject: Re: Making plpython 2 and 3 coexist a bit better