From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Need assistance for replication sync issue
Date: Thu, 19 Oct 2023 12:55:08 +0200
Message-ID: <4f6bd1b4459a1480e5938f40d4a752ca7edf4b2d.camel@cybertec.at> (raw)
In-Reply-To: <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
References: <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
On Thu, 2023-10-19 at 10:08 +0000, Veerendra Pulapa wrote:
> I need some help with a database issue we’re facing. We have a situation 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’s become
> a problem as we want our data to be as up-to-date as possible.
>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, veerendra.pulapa@ashnik.com
Subject: Re: Need assistance for replication sync issue
In-Reply-To: <4f6bd1b4459a1480e5938f40d4a752ca7edf4b2d.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox