Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id E987D632C0B for ; Fri, 30 Jan 2009 10:52:34 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 96258-08-3 for ; Fri, 30 Jan 2009 10:52:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id AA3BE632C30 for ; Fri, 30 Jan 2009 10:52:28 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n0UEqPqL008208; Fri, 30 Jan 2009 09:52:26 -0500 (EST) To: Jaume Sabater cc: pgsql-admin@postgresql.org Subject: Re: Warm standby recovery failure In-reply-to: <3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com> References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com> <14981.1233278521@sss.pgh.pa.us> <3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com> Comments: In-reply-to Jaume Sabater message dated "Fri, 30 Jan 2009 09:53:19 +0100" Date: Fri, 30 Jan 2009 09:52:25 -0500 Message-ID: <8207.1233327145@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/171 X-Sequence-Number: 31218 Jaume Sabater writes: > On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane wrote: >> We probably should add a caution about this to the manual's discussion >> of how to write archiving scripts. > I presume you mean the copy/transfer process did not do its job > correctly, Tom. Therefore, I would advise using a script that compares > the MD5/SHA1 sums of the origin and destination files and retries the > copy/transfer process before returning an exit status to the server > (archive_command call). Do you think this would suffice? That seems like using a sledgehammer to swat a fly. The problem as I saw it was that the script was probably simply not checking for an error result from 'cp'. regards, tom lane