Re: pg_stat_replication vs StandbyReplyMessage

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_replication vs StandbyReplyMessage
Date: 2012-08-15 15:39:30
Message-ID: 20120815153930.GG25473@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2012-08-15 15:41:38 Re: [COMMITTERS] pgsql: Revert "commit_delay" change; just add comment that we don't hav
Previous Message Andrew Dunstan 2012-08-15 15:37:04 Re: sha1, sha2 functions into core?