From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_stat_replication vs StandbyReplyMessage |
Date: | 2012-08-23 10:40:33 |
Message-ID: | CABUevEwYEmRpDe=NLeqd8dgpe-jqc1pN1fLfwvwpK6ZrbL+W=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 15, 2012 at 5:39 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, Aug 15, 2011 at 01:03:35PM +0200, Magnus Hagander 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?
>
> Did this ever get done? I don't think so, though everyone wanted it.
Nope, it wasn't done. Should probably do that for 9.3 (since adding a
field to pg_stat_replication will cause initdb, so we can't really do
it for 9.2 unless it was really critical - and it's not).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-08-23 10:47:36 | Re: alter enum add value if not exists |
Previous Message | Andres Freund | 2012-08-23 10:17:22 | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |