|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Magnus Hagander <magnus(at)hagander(dot)net>|
|Subject:||Re: pg_stat_replication vs StandbyReplyMessage|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Thu, Aug 23, 2012 at 12:40:33PM +0200, Magnus Hagander wrote:
> 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).
OK, TODO added:
Add entry creation timestamp column to pg_stat_replication
+ It's impossible for everything to be true. +
|Next Message||Bruce Momjian||2012-08-25 21:45:10||Re: timestamptz parsing bug?|
|Previous Message||Bruce Momjian||2012-08-25 20:25:45||Re: -Wformat-zero-length|