Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id DCA0A632CC3 for ; Tue, 3 Feb 2009 22:27:35 -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 14250-06 for ; Tue, 3 Feb 2009 22:27:24 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.180]) by mail.postgresql.org (Postfix) with ESMTP id 21A10632CBD for ; Tue, 3 Feb 2009 22:27:25 -0400 (AST) Received: by el-out-1112.google.com with SMTP id y26so1772253ele.10 for ; Tue, 03 Feb 2009 18:27:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=o/MXH3rIyIrjz80zoBNkhQJ/PlIhB2RJkocbvHoslOs=; b=oh0dTh2UnCtGN3LqoMfJdCG9BslAFFM3SdDcmLiU5DfcNPTe+5ZegU93t4Pr76+2Wp 9pGeiqH00/OmpqOQV0Sxx5k3LuHcn9Dd/O/2uIKXGgEn6V347Pd4SR4JHqKROzkjtjiM EDS2PD5/BLjf1jORH8Uz37h+VUm0/RYu9B2kg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QGs5nR1Yf1nbIhBXft+EkQXSP1v5Crao+UBwht/XH5Aplyiolv9wx7HQjZdmVfFqHV 5ILI1dZXPB40oFDvAzUVZmw3RxExokBTyHNZxil0z7bAv6SX31XsOQzn6V/gd+R7Nd5U GVZyNvQNrxtuz3jIW+//A7t8PDpymaYAHovnw= MIME-Version: 1.0 Received: by 10.151.99.3 with SMTP id b3mr2589747ybm.246.1233714443727; Tue, 03 Feb 2009 18:27:23 -0800 (PST) In-Reply-To: <8207.1233327145@sss.pgh.pa.us> References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com> <14981.1233278521@sss.pgh.pa.us> <3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com> <8207.1233327145@sss.pgh.pa.us> Date: Tue, 3 Feb 2009 19:27:23 -0700 Message-ID: Subject: Re: Warm standby recovery failure From: Scott Marlowe To: Tom Lane Cc: Jaume Sabater , pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 200902/34 X-Sequence-Number: 31255 On Fri, Jan 30, 2009 at 7:52 AM, Tom Lane wrote: > 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'. Plus, if you're using a system like rsync it uses checksums to make sure the data transferred is correct if you use the -c (think that's the one) switch. -- When fascism comes to America, it will be the intolerant selling it as diversity.