| From: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Cc: | ascot(dot)moss(at)gmail(dot)com |
| Subject: | Replication delay |
| Date: | 2013-08-10 20:51:08 |
| Message-ID: | 942DF7FF-967F-44FD-ADD1-4B6FBDAA8A0C@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hi,
I have a pair of PG servers, a master and a replica, all read-write queries are handled by the master, read-only ones are by the replica.
From time to time the replica itself is too busy, all read-only queries will get inconsistent results because of replication lag, sometimes it can be longer than 6 minutes. I am thinking to add multiple replicas to off-load read-only queries, can you please suggest a way to monitor and failover the read-only query when the replication lag in a replica is more than 5 minutes?
regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-10 21:04:42 | Re: Postgres 9.3 beta log |
| Previous Message | Stefan Kaltenbrunner | 2013-08-10 19:52:48 | Re: Postgres 9.3 beta log |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-10 21:04:42 | Re: Postgres 9.3 beta log |
| Previous Message | Stefan Kaltenbrunner | 2013-08-10 19:52:48 | Re: Postgres 9.3 beta log |