| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Timeout and Synch Rep |
| Date: | 2010-10-08 16:36:10 |
| Message-ID: | 4CAF487A.9090007@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> So, if something happens to the standby, and it cannot return an ack in
>> 30 seconds, they would like it to degrade to asynch mode. At that
>> point, they would also like to trigger a nagios alert which will wake up
>> the sysadmin with flashing red lights.
>
> How?
TBD, and before 9.1. It's clear to *me* that we're going to need some
read-only system views around replication in order to make monitoring
work. Also, given that we have this shiny new LISTEN/NOTIFY
implementation, it would be peachy keen to maybe make use of it to emit
an event when replication changes, no?
Otherwise, DBAs are forced to tail the logs to figure out what
replication status is. This is NOT adequate.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-10-08 16:41:08 | Re: Issues with Quorum Commit |
| Previous Message | Josh Berkus | 2010-10-08 16:29:59 | Re: standby registration (was: is sync rep stalled?) |