Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\))
Subject: Re: Parallelize WAL Sender and WAL receiver
From: Rui DeSousa <rui.desousa@icloud.com>
In-Reply-To: 
 <CACXtxt_ANB20ZWjFQt=BOtCN50g6MvNvQPokv5TwPSwwXchdkw@mail.gmail.com>
Date: Wed, 4 Sep 2024 21:52:01 -0400
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBFF3C3E-A54A-4210-91A5-B8926059B618@icloud.com>
References: 
 <CACXtxt_ANB20ZWjFQt=BOtCN50g6MvNvQPokv5TwPSwwXchdkw@mail.gmail.com>
To: Karthik Yellapragada <karthik.yellapragada@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/EBFF3C3E-A54A-4210-91A5-B8926059B618%40icloud.com>
Precedence: bulk


> On Sep 4, 2024, at 9:03 PM, Karthik Yellapragada =
<karthik.yellapragada@gmail.com> wrote:
>=20
> Hello all,
>=20
> I frequently face the problem of wals generated faster than the wals =
transferred and applied.
>=20
> Is there a way to speed up the process? So I don=E2=80=99t accumulate =
a lot of WALs at the primary?
>=20
> Regards,
> Karthik.

What do you mean by parallelized WAL sender? Do you have many replicas =
connecting to the primary? Have you tried cascading replication?

What=E2=80=99s 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 replication exceeded an acceptable delay to =
ensure SLA  where met.  It is faster to pull the WAL files from the =
local archive which where already replicated to London than streaming =
replication over a high latency WAN.  After It catches up, it will =
reconnect to streaming replication. =20