References: <53B44151.4030200@gmail.com>
Message-ID: <1404328408.71750.YahooMailNeo@web122305.mail.ne1.yahoo.com>
Date: Wed, 2 Jul 2014 12:13:28 -0700
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: WAL archiving to 2 standby servers
To: John Scalia <jayknowsunix@gmail.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <53B44151.4030200@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

John Scalia <jayknowsunix@gmail.com> wrote:

> 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. The=
se
> machines are configured to be
> streaming replication and I've got the archive command on the primary doi=
ng
> 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?

What I have done in a situation like this is to have the archive
command copy to a directory on the database server machine, and use
rsync to make copies on all targets.=A0 If you try to have the
archive command deal with both standby machines directly, it gets
pretty complicated trying to handle the failure of one of those
standby machines, or of the network connecting to one of them.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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