| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| 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: | 2011-08-15 11:50:58 |
| Message-ID: | CA+TgmoZX_Q8rg6LV=Kg7vRJNMEEOii_VZHdo-wT+=QDR=8FdUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-08-15 11:52:21 | Re: Online base backup from the hot-standby |
| Previous Message | Joachim Wieland | 2011-08-15 11:30:10 | Re: synchronized snapshots |