Message-ID: <4f6bd1b4459a1480e5938f40d4a752ca7edf4b2d.camel@cybertec.at>
Subject: Re: Need assistance for replication sync issue
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>, pgsql-admin
	 <pgsql-admin@postgresql.org>
Date: Thu, 19 Oct 2023 12:55:08 +0200
In-Reply-To: 
 <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
References: 
	<SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/4f6bd1b4459a1480e5938f40d4a752ca7edf4b2d.camel%40cybertec.at>
Precedence: bulk

On Thu, 2023-10-19 at 10:08 +0000, Veerendra Pulapa wrote:
> I need some help with a database issue we=E2=80=99re facing. We have a si=
tuation where
> our primary data center and our disaster recovery site are far apart, and=
 this
> long distance is causing delays in keeping our data synchronized. It=E2=
=80=99s become
> a problem as we want our data to be as up-to-date as possible.
>=20
> Do you have any suggestions for dealing with this kind of situation?

Yes: don't use synchronous replication.

You are fighting with physics (speed of light), not with an implementation
deficiency.  You cannot win that fight.

Yours,
Laurenz Albe