From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Need assistance for replication sync issue
Date: Thu, 19 Oct 2023 07:36:50 -0500
Message-ID: <0253c15b-a75e-4bc6-9049-8224d0ceb9e2@gmail.com> (raw)
In-Reply-To: <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
References: <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
On 10/19/23 05:08, Veerendra Pulapa wrote:
> Hello,
>
> 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? We’ve
> tried a few things, but we’re still struggling with the replication delays
> caused by the high latency between the sites.
>
> Note: Bandwidth is very low and latency is very high.
>
> I’d appreciate any advice you can provide.
/Never/ use /synchronous/ replication over a WAN. Not only because
"physics", as Laurenz mentions, but also because WAN links can be /slow/,
and break more often than LAN links.
Thus, use "async" replication instead.
--
Born in Arizona, moved to Babylonia.
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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Need assistance for replication sync issue
In-Reply-To: <0253c15b-a75e-4bc6-9049-8224d0ceb9e2@gmail.com>
* 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