Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eemBt-0005ef-UJ for pgsql-admin@arkaria.postgresql.org; Thu, 25 Jan 2018 18:24:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eemBt-0002zd-Ai for pgsql-admin@arkaria.postgresql.org; Thu, 25 Jan 2018 18:24:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eemBs-0002zR-JS for pgsql-admin@lists.postgresql.org; Thu, 25 Jan 2018 18:24:01 +0000 Received: from omr-a008e.mx.aol.com ([204.29.186.51]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eemBo-0008UF-Ps for pgsql-admin@postgresql.org; Thu, 25 Jan 2018 18:23:58 +0000 Received: from mtaomg-mca01.mx.aol.com (mtaomg-mca01.mx.aol.com [172.26.221.79]) by omr-a008e.mx.aol.com (Outbound Mail Relay) with ESMTP id A99BD38000A7; Thu, 25 Jan 2018 13:23:54 -0500 (EST) Received: from core-aab02g.mail.aol.com (core-aab02.mail.aol.com [172.27.9.2]) by mtaomg-mca01.mx.aol.com (OMAG/Core Interface) with ESMTP id 519A238000082; Thu, 25 Jan 2018 13:23:54 -0500 (EST) Received: from 208.185.19.251 by webjas-vae073.srv.aolmail.net (10.96.23.76) with HTTP (WebMailUI); Thu, 25 Jan 2018 13:23:54 -0500 Date: Thu, 25 Jan 2018 13:23:54 -0500 From: Rakesh Kumar To: azimeiu@gmail.com, pgsql-admin@postgresql.org, pgsql-general@postgresql.org Message-Id: <1612e8fd701-1722-18849@webjas-vae073.srv.aolmail.net> In-Reply-To: Subject: Re: Sync replication MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_132366_368099017.1516904634113" X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [208.185.19.251] x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1516904634; bh=t4eIUSkGdskM7esamzEcVqZ/DPSOvg972gWetF8MNLA=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=s19GjhPFSSR2zcwmiCs46cO6FsG2J5bfCI//AhuXkRKNv0UawRu2HI4KStZCVbFti rvB71Y92imhuhdXRRoym6RzUpYG355jD2IrzSpvLv8UJ5uewNdtQWrk/kGOHn1f/Ba CV5TOl+a+MjERg9UcKko981AYvg5HUSwIKFcaSDA= x-aol-sid: 3039ac1add4f5a6a20ba39c6 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_132366_368099017.1516904634113 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit >I have a question regarding synchronus replication. >If i have a master and standby server will sync replication setup..when my slave dies and master is still active. Will the transaction completes, or >master will wait for slave to commit the transaction and then commits its. ? Master will wait for slave to come back up. PG"s replication is not the same as SQLServer/DB2/Oracle where they allow master to continue operating while the slave is down. useful during scheduled maintenance. ------=_Part_132366_368099017.1516904634113 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

>I have a question regarding synchronus replication. 
>If i have a master and standby server will sync replication setup..when my slave dies and master is still active. Will the transaction completes, or >master will wait for slave to commit the transaction and then commits its. ?

Master will wait for slave to come back up.  PG"s replication is not the same as SQLServer/DB2/Oracle 
where they allow master to continue operating while the slave is down.  useful during scheduled maintenance.

------=_Part_132366_368099017.1516904634113--