From: Dianne Skoll <dfs@roaringpenguin.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: What causes streaming replication delay?
Date: Wed, 31 Aug 2016 13:16:04 -0400
Message-ID: <20160831131604.0f305404@hydrogen.roaringpenguin.com> (raw)
In-Reply-To: <CAHw75vtu-Mxjp1uFB1iQctnT9Tew72=OgBE9sVO4mW+kHZEDKw@mail.gmail.com>
References: <20160831114417.7fc1040d@hydrogen.roaringpenguin.com>
<CAHw75vtu-Mxjp1uFB1iQctnT9Tew72=OgBE9sVO4mW+kHZEDKw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Wed, 31 Aug 2016 12:04:23 -0400
Keith <keith@keithf4.com> wrote:
> All depends on how you're monitoring your slave lag. Check this blog
> post and if you're seeing actual byte lag, then you could have cause
> for concern.
It's not because the master is idle... there is tons of write traffic.
And the way I measure the lag is about as directly as you can: I
periodically insert a timestamp into a specific table on the master,
and then poll the hot-standby until the inserted timestamp has
appeared.
Regards,
Dianne.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: dfs@roaringpenguin.com
Subject: Re: What causes streaming replication delay?
In-Reply-To: <20160831131604.0f305404@hydrogen.roaringpenguin.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox