Skip site navigation (1) Skip section navigation (2)

Re: Measuring replication lag time

From: Samba <saasira(at)gmail(dot)com>
To: Stuart Bishop <stuart(at)stuartbishop(dot)net>
Cc: Greg Williamson <gwilliamson39(at)yahoo(dot)com>, "List, Postgres" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Measuring replication lag time
Date: 2012-02-24 14:39:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
> Comparing "pg_controldata" output on prod and standby might help you with
> this.

We do use this approach and it is pretty reliable and gives time lag up to
the granularity of checkpoint_timeout.

On Thu, Feb 23, 2012 at 11:51 AM, Stuart Bishop <stuart(at)stuartbishop(dot)net>wrote:

> On Thu, Feb 23, 2012 at 2:58 AM, Greg Williamson
> <gwilliamson39(at)yahoo(dot)com> wrote:
> > Stuart Bishop shaped the aether to ask:
> >
> >> Hi.
> >>
> >> I need to measure how far in the past a hot standby is, async
> >> streaming replication.
> >
> > Not sure if this will help, but we are using repmgr <
>>; it sets up a monitoring
> schema which we poll )see the "Monitoring and Testing" section ... study
> their source code some and see how they come up with lag times.
> Might help indeed. My existing solution already has a small daemon (I
> can't always query the Slony-I sl_status view fast enough for load
> balancing web requests, so I maintain a cache). But repmgr seems to
> cover other work I need to do to keep ops happy so something for me to
> look closer at.
> --
> Stuart Bishop <stuart(at)stuartbishop(dot)net>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:

In response to

pgsql-general by date

Next:From: James B. ByrneDate: 2012-02-24 15:16:47
Subject: Having a problem with RoR-3.1.1 and Pg-0.1
Previous:From: Vick KheraDate: 2012-02-24 14:36:38
Subject: Re: Configuring for very slow I/O

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group