Re: Replication delay

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Replication delay
Date: 2013-08-11 13:50:43
Message-ID: CAB7nPqRWCYB264Lwg1FRQPRHKyEWJBejqo=ej-SmLZJZNjoCfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Sun, Aug 11, 2013 at 5:51 AM, ascot(dot)moss(at)gmail(dot)com
<ascot(dot)moss(at)gmail(dot)com> wrote:
> 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?
I assume that you could use pgpool for that. It has some monitoring
features for replication delay and it can do read-only load balancing
among several servers. You also shouldn't need to change your
application.
Have a look at its documentation to make an opinion:
http://pgpool.projects.pgfoundry.org/pgpool-II/doc/pgpool-en.html

Regards,
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Nolan 2013-08-11 15:27:02 Re: incremental dumps
Previous Message Jov 2013-08-11 11:36:33 Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2013-08-11 16:26:47 Re: [PATCH] pg_sleep(interval)
Previous Message Jov 2013-08-11 11:36:33 Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376