Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42588=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X2OL5-000524-Fh
 for pgsql-admin@arkaria.postgresql.org; Wed, 02 Jul 2014 17:28:59 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42588=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X2OL4-0000be-Ur
 for pgsql-admin@arkaria.postgresql.org; Wed, 02 Jul 2014 17:28:58 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1X2OL3-0000Zf-Ju
 for pgsql-admin@postgresql.org; Wed, 02 Jul 2014 17:28:57 +0000
Received: from mail-yh0-x229.google.com ([2607:f8b0:4002:c01::229])
 by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1X2OL0-0001ov-9e
 for pgsql-admin@postgresql.org; Wed, 02 Jul 2014 17:28:56 +0000
Received: by mail-yh0-f41.google.com with SMTP id z6so7098100yhz.28
 for <pgsql-admin@postgresql.org>; Wed, 02 Jul 2014 10:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject
 :content-type:content-transfer-encoding;
 bh=t3MjYnaku5+0HP3XQaIbsafslCydfEsCCIXkmX4jvnI=;
 b=NutibZOa7M3Npw78uy9hQvGP+Rmkhzzx1dN243Y3eeNqLJY6dNgSSCR3E0Q0GUAtsQ
 fN2DsgeDGAIkRiZ8ZkkLwN4qkQp3eGXbRydwFhz6kmiuET8dEDiU+wRiIqO4tGYt2isI
 wtGLwm+xwcNgWuRThT6XwsLyl9neGMJISif+7RV0lKNcjMGCKPKR0WvfV0QDB3/oxWQ7
 i0ybaa8XQ7KTsza4lCeToJoa/o1nBrLASU5kYqPL1P8tL41x7q0Zf5uL5/8riqPShD+4
 WJBJjJgMmCtRybdHVGXi8Zr9awueDMnY02MbfBDLVnlJbn9922xph4WUKegS6s8o5+0s
 enAg==
X-Received: by 10.236.134.74 with SMTP id r50mr81797133yhi.2.1404322132080;
 Wed, 02 Jul 2014 10:28:52 -0700 (PDT)
Received: from [192.168.254.4] (h77.89.102.166.static.ip.windstream.net.
 [166.102.89.77])
 by mx.google.com with ESMTPSA id o69sm35107535yho.19.2014.07.02.10.28.51
 for <pgsql-admin@postgresql.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 02 Jul 2014 10:28:51 -0700 (PDT)
Message-ID: <53B44151.4030200@gmail.com>
Date: Wed, 02 Jul 2014 13:28:49 -0400
From: John Scalia <jayknowsunix@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: WAL archiving to 2 standby servers
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi all,

I'm wondering as I've never seen anyone doing this if I can/should setup WAL archiving from the primary server to 2 different standby servers. These machines are configured to be 
streaming replication and I've got the archive command on the primary doing an scp to both standbys, but for some reason the second one isn't getting anything. What the 
archive_command looks like is "scp %p user@standby1:/<dir>/%f; scp %p user@standby2:<dir>/%f". That's not wokring correctly, but I'm wondering if it's even necessary for the 2nd 
standby?

Just askin',
Jay

PS. There are two standby's to deal with the problem of synchronous_commit and the failure of one of the standby's.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin