Re: Replication Testing- How to introduce a Lag

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: "Subramanian,Ramachandran" <ramachandran(dot)subramanian(at)alte-leipziger(dot)de>, "pgsql-novice(at)lists(dot)postgresql(dot)org" <pgsql-novice(at)lists(dot)postgresql(dot)org>
Subject: Re: Replication Testing- How to introduce a Lag
Date: 2026-03-24 16:41:51
Message-ID: 2fb6a2f5eb2c9a1cbe701a237c74223d121ca918.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Tue, 2026-03-24 at 07:51 +0000, Subramanian,Ramachandran wrote:
> 3. If not caught up, how many bytes / KB worth of data needs to be replicated

Please define "caught up", in particular how you understand the term
in the presence of recovery_min_apply_delay, which you said you are setting.
The point of the parameter is to *prevent* WAL replay from catching up.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Subramanian,Ramachandran 2026-03-24 17:01:07 AW: Replication Testing- How to introduce a Lag
Previous Message Subramanian,Ramachandran 2026-03-24 07:51:57 AW: Replication Testing- How to introduce a Lag