> On Sep 4, 2024, at 9:03 PM, Karthik Yellapragada <karthik.yellapragada@gmail.com> wrote:
>
> Hello all,
>
> I frequently face the problem of wals generated faster than the wals transferred and applied.
>
> Is there a way to speed up the process? So I don’t accumulate a lot of WALs at the primary?
>
> Regards,
> Karthik.
What do you mean by parallelized WAL sender? Do you have many replicas connecting to the primary? Have you tried
cascadingreplication?
What’s the network between the systems? Is a WAN with high latency? Can the replica pull from the WAL file from an
archive? For a high latency networks like New York to London; I would terminate the WAL receiver via a script if
replicationexceeded an acceptable delay to ensure SLA where met. It is faster to pull the WAL files from the local
archivewhich where already replicated to London than streaming replication over a high latency WAN. After It catches
up,it will reconnect to streaming replication.
