Request a Demo
Home   >   mailing lists

Re: Replication Testing- How to introduce a Lag - Mailing list pgsql-novice

From Laurenz Albe
Subject Re: Replication Testing- How to introduce a Lag
Date
Msg-id 2fb6a2f5eb2c9a1cbe701a237c74223d121ca918.camel@cybertec.at
Whole thread Raw
In response to AW: Replication Testing- How to introduce a Lag  ("Subramanian,Ramachandran" <ramachandran.subramanian@alte-leipziger.de>)
Responses AW: Replication Testing- How to introduce a Lag
List pgsql-novice
Tree view 
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

pgsql-novice by date:

Previous
From: "Subramanian,Ramachandran"
Date:
Subject: AW: Replication Testing- How to introduce a Lag
Next
From: "Subramanian,Ramachandran"
Date:
Subject: AW: Replication Testing- How to introduce a Lag