Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 38ACB2E0049 for ; Tue, 25 Mar 2008 21:26:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 82502-08 for ; Tue, 25 Mar 2008 21:25:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by postgresql.org (Postfix) with ESMTP id C255F2E005A for ; Tue, 25 Mar 2008 21:25:57 -0300 (ADT) Received: from mailsrv.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id 81FA3BC4 for ; Wed, 26 Mar 2008 01:42:41 +0100 (CET) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id DE3B0BF96 for ; Wed, 26 Mar 2008 01:25:39 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton? Date: Wed, 26 Mar 2008 01:25:51 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <84D57263D486374587DA0820E60A2CC601B07E23@srit_mail.renaissance-it.com> <9abe84da0802271254j3a6463c8j7ccbe603bcdbf477@mail.gmail.com> <47C5D0AB.7070102@quietcaresystems.com> In-Reply-To: <47C5D0AB.7070102@quietcaresystems.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4934899.eVHUorpYD3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200803260125.51185@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.044 tagged_above=0 required=5 tests=AWL=0.044 X-Spam-Level: X-Archive-Number: 200803/221 X-Sequence-Number: 28704 --nextPart4934899.eVHUorpYD3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mittwoch, 27. Februar 2008 salman wrote: > archive_command =3D 'gzip %p; rsync -av %p.gz -e \"ssh -p portNum -i > /home/postgres/.ssh/id_dsa\" > postgres@rhostname:/usr/local/postgresql/archives/recovery/%f.gz && > rm -f %p.gz' This works as long as there are no transmission errors. What can be done=20 to work around network problems? Example: when one rsync above does not=20 work, that log is never transmitted to the other host. Does somebody=20 have a sophisticated script for that? mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart4934899.eVHUorpYD3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBH6ZgPzhSR9xwSCbQRAtI2AJ0Wn5XIgN/KALd53GWA47iyyirXFgCgotx3 JluyA/zNpIRdBOkBqa2o69Q= =+QlQ -----END PGP SIGNATURE----- --nextPart4934899.eVHUorpYD3--