Re: pg_stat_replication vs StandbyReplyMessage
От | Magnus Hagander |
---|---|
Тема | Re: pg_stat_replication vs StandbyReplyMessage |
Дата | |
Msg-id | CABUevEwTc0uaRxEFr-LVDho9KUmWZMW_8hv=SghwJd9yUtPM0w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_stat_replication vs StandbyReplyMessage (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: pg_stat_replication vs StandbyReplyMessage
|
Список | pgsql-hackers |
On Mon, Aug 15, 2011 at 13:50, Robert Haas <robertmhaas@gmail.com> wrote: > 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. 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/
В списке pgsql-hackers по дате отправления: