Content-Type: multipart/alternative;
 boundary="------------vII0W4kb88gHVK9zIsohg0ck"
Message-ID: <0253c15b-a75e-4bc6-9049-8224d0ceb9e2@gmail.com>
Date: Thu, 19 Oct 2023 07:36:50 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Need assistance for replication sync issue
Content-Language: en-US
To: pgsql-admin@lists.postgresql.org
References: 
 <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
From: Ron <ronljohnsonjr@gmail.com>
In-Reply-To: 
 <SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM>
Archived-At: 
 <https://www.postgresql.org/message-id/0253c15b-a75e-4bc6-9049-8224d0ceb9e2%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------vII0W4kb88gHVK9zIsohg0ck
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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.
--------------vII0W4kb88gHVK9zIsohg0ck
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    On 10/19/23 05:08, Veerendra Pulapa wrote:<br>
    <blockquote type="cite"
cite="mid:SE1P216MB2309AF940B72477BB9B10738F1D4A@SE1P216MB2309.KORP216.PROD.OUTLOOK.COM">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>
          <div>Hello,
            <div dir="ltr"><br>
            </div>
            <div>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.</div>
            <div dir="ltr"><br>
            </div>
            <div>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.</div>
            <div dir="ltr"><br>
            </div>
            <div dir="ltr">Note: Bandwidth is very low and latency is
              very high.</div>
            <div dir="ltr"><br>
            </div>
            <div>I’d appreciate any advice you can provide.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <i>Never</i> use <i>synchronous</i> replication over a WAN.  Not
    only because "physics", as Laurenz mentions, but also because WAN
    links can be <i>slow</i>, and break more often than LAN links.<br>
    <br>
    Thus, use "async" replication instead.<br>
    <br>
    <div class="moz-signature">-- <br>
      Born in Arizona, moved to Babylonia.</div>
  </body>
</html>

--------------vII0W4kb88gHVK9zIsohg0ck--