Re: pg_stat_replication vs StandbyReplyMessage - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_stat_replication vs StandbyReplyMessage
Date
Msg-id CA+TgmoZX_Q8rg6LV=Kg7vRJNMEEOii_VZHdo-wT+=QDR=8FdUg@mail.gmail.com
Whole thread Raw
In response to pg_stat_replication vs StandbyReplyMessage  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_stat_replication vs StandbyReplyMessage
List pgsql-hackers
On Mon, Aug 15, 2011 at 7:03 AM, Magnus Hagander <magnus@hagander.net> wrote:
> The pg_stat_replication view exposes all the fields in
> StandbyReplyMessage *except* for the timestamp when the message was
> generated. On an active system this is not all that interesting, but
> on a mostly idle system that allows the monitoring to react faster
> than the timeout that actually kicks the other end off - and could be
> useful in manual debugging scenarios. Any particular reason why this
> was not exposed as it's own column?

I wondered the same thing.  Sounds like a good idea.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Joachim Wieland
Date:
Subject: Re: synchronized snapshots
Next
From: Robert Haas
Date:
Subject: Re: Online base backup from the hot-standby