Re: pg_stat_replication vs StandbyReplyMessage

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_replication vs StandbyReplyMessage
Date: 2011-08-16 09:51:33
Message-ID: CABUevEwTc0uaRxEFr-LVDho9KUmWZMW_8hv=SghwJd9yUtPM0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 15, 2011 at 13:50, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Aug 15, 2011 at 7:03 AM, Magnus Hagander <magnus(at)hagander(dot)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.

I can go do that. Care to argue^Wbikeshed for a specific name?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Anssi Kääriäinen 2011-08-16 10:24:25 Re: index-only scans
Previous Message Dimitri Fontaine 2011-08-16 09:35:10 Re: some missing internationalization in pg_basebackup