Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vjqvu-0006C2-Da for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2013 13:38:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vjqvt-0006ie-OY for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2013 13:38:05 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vjqvs-0006iV-31 for pgsql-general@postgresql.org; Fri, 22 Nov 2013 13:38:04 +0000 Received: from mail-wi0-x22c.google.com ([2a00:1450:400c:c05::22c]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vjqvo-00028F-KJ for pgsql-general@postgresql.org; Fri, 22 Nov 2013 13:38:03 +0000 Received: by mail-wi0-f172.google.com with SMTP id en1so723921wid.5 for ; Fri, 22 Nov 2013 05:37:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hMed85LazwJPoWAzmajGgwA4GjHyWFwkQ6ygf2dbbtA=; b=rRh56i0j1cEJmUwbN9Fh3RIXXpX1gzvtS8Nh6mQAX46/S1a6h46OupKU04ijqXYthX 7Mp5tccdVCm9BjzCoMjn2qTf0QV15YjMUsd4YQWpwbQYVJmrA4LJE2/KyV9UzFAKxNfi LX8r8LGkgGCCajGFFj1/3/DAxdYdov+HtXMxKVX3ct2gAY8zHDMpbsHEtwT6ddA9HtjN AFGJgarP4Ghy3Gboo10MGYLB4sqzJvQ1f7+ownc+Lply0An54tDvRFG0RFX44RlX1R4k X6+sQ+Uvkf2GHJH00ThUYV+scjFnf317SpOPWSSiG7dVH9kPbBch6tahuY5FvoalWlP2 +iAA== MIME-Version: 1.0 X-Received: by 10.194.20.202 with SMTP id p10mr10901537wje.39.1385127479135; Fri, 22 Nov 2013 05:37:59 -0800 (PST) Received: by 10.180.75.111 with HTTP; Fri, 22 Nov 2013 05:37:59 -0800 (PST) In-Reply-To: References: <528F4BE2.7000400@gmx.net> Date: Fri, 22 Nov 2013 22:37:59 +0900 Message-ID: Subject: Re: PG replication across DataCenters From: Michael Paquier To: Kaushal Shriyan Cc: Albe Laurenz , =?ISO-8859-1?Q?Torsten_F=F6rtsch_=2AEXTERN=2A?= , "pgsql-general@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On Fri, Nov 22, 2013 at 10:03 PM, Kaushal Shriyan wrote: > I am not sure i understand the difference between async and sync replication > and on what scenarios i should use async or sync replication. Does it mean > if it is within same DC then sync replication is the best and if it is > across DC replication async is better than sync. Please help me understand. In the case of synchronous replication, master node waits for the confirmation that a given transaction has committed on slave side before committing itself. This wait period can cause some delay, hence it is preferable to use sync replication with nodes that far from each other. -- Michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general