Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZCWwK-0007AK-9t for pgsql-admin@arkaria.postgresql.org; Tue, 07 Jul 2015 17:45:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZCWwJ-0007gz-B9 for pgsql-admin@arkaria.postgresql.org; Tue, 07 Jul 2015 17:45:51 +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) (envelope-from ) id 1ZCWwH-0007eR-Iy for pgsql-admin@postgresql.org; Tue, 07 Jul 2015 17:45:49 +0000 Received: from mail-ig0-f173.google.com ([209.85.213.173]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZCWwF-0008HO-0B for pgsql-admin@postgresql.org; Tue, 07 Jul 2015 17:45:48 +0000 Received: by igcqs7 with SMTP id qs7so38210926igc.0 for ; Tue, 07 Jul 2015 10:45:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type; bh=9+4SEAHWJw75N7otmuq4Ewt7jvb7qGBuCzf83ypjrXk=; b=SQ4HNxeCQBqoaRt6T1j2BXNagKmGO8GvXrEkWspoEw7A816XkQmkLD6tMZH59csYZJ lbcyITt68zWStwzFFRt8PTJApPjmXndiimYPz2lhLVs1sjJZmEM5/YfPCCcJO5jx/wjU bBR1Ugb3QXHf8xsul2aCOXVQ4esJqvr/9IVlOUYgFg8Ur9/GNxnuEu/N9RTSt9OEu3HL y55ZO9J8Ip+3n3pAo4Vct4rv0ukAO4JsHHl4vjzvJvUTySB2bWDPtygYGYLqGgTgw3iD SygTdxj/qe1WYy7+o/02h+rh100PPm+qGDpcaxHHbuBrKLBjC6cnj7ScTBl14F9Xf3A/ x8cw== X-Gm-Message-State: ALoCoQnYXy0Bk7YILntJJWDxXAsS4trIc4XZZJn9DwBJ+nTB1DgYwwS0wynrQcjRp1fAeYqZ4bsO X-Received: by 10.107.8.7 with SMTP id 7mr8348836ioi.15.1436291145835; Tue, 07 Jul 2015 10:45:45 -0700 (PDT) Received: from [10.16.0.110] ([50.246.199.241]) by mx.google.com with ESMTPSA id f126sm15049190ioe.21.2015.07.07.10.45.43 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Jul 2015 10:45:44 -0700 (PDT) Message-ID: <559C1046.6010007@consistentstate.com> Date: Tue, 07 Jul 2015 11:45:42 -0600 From: CS DBA User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Synchronous replication question Content-Type: multipart/alternative; boundary="------------000806010805030504040502" X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------000806010805030504040502 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit All; The docs specify this (9.4 docs): Synchronous replication offers the ability to confirm that all changes made by a transaction have been transferred to /*one*/ synchronous standby server. This extends the standard level of durability offered by a transaction commit. This level of protection is referred to as 2-safe replication in computer science theory. Does this mean that Synchronous replication only works with one standby? Thanks in advance --------------000806010805030504040502 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit All;

The docs specify this (9.4 docs):

Synchronous replication offers the ability to confirm that all changes made by a transaction have been transferred to one synchronous standby server. This extends the standard level of durability offered by a transaction commit. This level of protection is referred to as 2-safe replication in computer science theory.

Does this mean that Synchronous replication only works with one standby?

Thanks in advance
--------------000806010805030504040502--