Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 84527632CB8 for ; Tue, 3 Feb 2009 19:39:29 -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 45471-05 for ; Tue, 3 Feb 2009 19:39:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mail.postgresql.org (Postfix) with ESMTP id 91BD9632C73 for ; Tue, 3 Feb 2009 19:39:26 -0400 (AST) Received: by gxk14 with SMTP id 14so2381010gxk.19 for ; Tue, 03 Feb 2009 15:39:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.189.2 with SMTP id m2mr26250ybf.11.1233697255056; Tue, 03 Feb 2009 13:40:55 -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 16:40:55 -0500 Message-ID: <16b031c0902031340j2467e238u9028485a8ef61043@mail.gmail.com> Subject: Re: Warm standby recovery failure From: Lee Azzarello To: 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/27 X-Sequence-Number: 31248 thank you all for your help. It was indeed my copy script that destroyed the database. I now understand that postgresql shouldn't be concerned with validating a WAL segment, that's the responsibility of the script that hands the segment to postgres. -lee On Fri, Jan 30, 2009 at 9: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'. > > regards, tom lane > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin >