Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 2905062E7C6 for ; Fri, 30 Jan 2009 04:53:24 -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 14857-05 for ; Fri, 30 Jan 2009 04:53:21 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mail.postgresql.org (Postfix) with ESMTP id 29448632A1D for ; Fri, 30 Jan 2009 04:53:21 -0400 (AST) Received: by ewy14 with SMTP id 14so739676ewy.19 for ; Fri, 30 Jan 2009 00:53:19 -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:content-type :content-transfer-encoding; bh=zYlfRVkLSbs7ltj8mwIiaL02ITBOjMmxP+UaIZpLsKo=; b=tf3cQX3qDWRg21pmtpuqsjRqF+zaSwhC+4WutVCrwXp357X67lzldQlM11C1X+bLzz B7wAbEQmWYWbscXT3UssKeCeUl11vUBs6Eb1deeOoxXtdpN85UjJJdvWjdir62KzbYVE FXTw9eQyFWjksNpY6g3VvxiQOooHGEprdB0UA= 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 :content-type:content-transfer-encoding; b=Cede/0rrAq6AuBAsvDSZCMkWV7jy2zt2JgeXqmzwAf0cQLmPOvT8w0n/t8f+zj0K+6 vmgySAWMzRaWxNzr7jqTC6phE7Sd397wtBspZkMtdbfsjGWSxUuc0PfAU+DN2jf6NtFh eBMt+S8FkoVeJ25NaEqM1OwSE4y4RvrGM4JBo= MIME-Version: 1.0 Received: by 10.103.106.1 with SMTP id i1mr479120mum.47.1233305599116; Fri, 30 Jan 2009 00:53:19 -0800 (PST) In-Reply-To: <14981.1233278521@sss.pgh.pa.us> References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com> <14981.1233278521@sss.pgh.pa.us> Date: Fri, 30 Jan 2009 09:53:19 +0100 Message-ID: <3786f7bb0901300053s20fb930bv76c0bb46479be7fe@mail.gmail.com> Subject: Re: Warm standby recovery failure From: Jaume Sabater To: pgsql-admin@postgresql.org Content-Type: text/plain; charset=UTF-8 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: 200901/166 X-Sequence-Number: 31213 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? -- Jaume Sabater http://linuxsilo.net/ "Ubi sapientas ibi libertas"