public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nick Cleaton <[email protected]>
To: Jon Zeppieri <[email protected]>
Cc: [email protected]
Subject: Re: Possible causes of high_replay lag, given replication settings?
Date: Wed, 23 Jul 2025 21:27:44 +0100
Message-ID: <CAFgz3ksSB1OvN1ONDOO2qvhhF-FS7PXQTQtkDQYP_Y_pcvf+6g@mail.gmail.com> (raw)
In-Reply-To: <CAKfDxxwF03mouH7GqdZ0AqpGKz2wTj4T3F6ei_ubEQnNtErfGA@mail.gmail.com>
References: <CAKfDxxwF03mouH7GqdZ0AqpGKz2wTj4T3F6ei_ubEQnNtErfGA@mail.gmail.com>

On Fri, 18 Jul 2025 at 21:29, Jon Zeppieri <[email protected]> wrote:
>
> I just had a situation where physical replication fell far behind
> (hours). The write and flush lag times were 0, but replay_lag was
> high. The replica has hot_standby_feedback on, and both
> max_standby_streaming_delay and max_standby_archive_delay are set to
> 30s.
>
> What could cause a situation like this? If the network were a problem,
> I'd expect the other _lag times to be high. So it appears that the
> replica was getting the WAL but was unable to apply it. Are there
> situations where the replica cannot apply WAL other than the kinds of
> conflicts that would be addressed by the _delay settings?
>
> I checked pg_stat_database_conflicts, but there was nothing in it -- all zeros.

This can happen when there are several busy writing processes on the
primary. The single replay process on the replica can't keep up with
the writes.

view thread (2+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Possible causes of high_replay lag, given replication settings?
  In-Reply-To: <CAFgz3ksSB1OvN1ONDOO2qvhhF-FS7PXQTQtkDQYP_Y_pcvf+6g@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox