Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id C7892632517 for ; Thu, 25 Mar 2010 10:44:07 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 10697-07 for ; Thu, 25 Mar 2010 13:43:47 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com [209.85.220.224]) by mail.postgresql.org (Postfix) with ESMTP id 04CEE632636 for ; Thu, 25 Mar 2010 10:43:55 -0300 (ADT) Received: by fxm24 with SMTP id 24so3107744fxm.3 for ; Thu, 25 Mar 2010 06:43:54 -0700 (PDT) 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; bh=WX5VGS9sduXsaPfUA2TqXD7PsB5lnVUpl2diwNK+K3M=; b=kaSPJQbPBY8TPtV6C4rC8QESvUrcswERkEc+yMoGY4iNgxW78OMQz3KvLYCF0JgKly l4pGAAg19n+Pht0dYkJ9ZhkePMnxS3Mc4kBJS9BoNq3Uq4WkIRJ21sVAqyMiAh8UBTyw 1fOdC6irwobuIYAomBfJq0yaYc4UBwAWesp98= 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; b=dTz65qGmEXF+Otkhn1D2kRMuCzGQp9xnV9gopgqAcygBIc0kSJAW6B2ygOEsm9GXPI silasifWULm7APaVUd61Bxjxcle1+pmNAkGLVQU1ofyZWLJzhxFAZClDmONX6vLcT/wB 20JFBOpxULKSWIrZZYAWAmZJXQ7pr4FHsAJCw= MIME-Version: 1.0 Received: by 10.239.184.9 with SMTP id w9mr422962hbg.120.1269524633322; Thu, 25 Mar 2010 06:43:53 -0700 (PDT) In-Reply-To: <4BAB5D4E.4000009@enterprisedb.com> References: <3f0b79eb1002092105r21e009d3v468496058ba04392@mail.gmail.com> <4BA0B079.3050301@enterprisedb.com> <3f0b79eb1003180727g7877743eq81274e014fe70a49@mail.gmail.com> <1268988724.3556.3.camel@ebony> <4BA361E4.7020309@enterprisedb.com> <3f0b79eb1003230017v16f4ecbeyc20e75beeffe8f1c@mail.gmail.com> <4BAA060A.2020000@enterprisedb.com> <3f0b79eb1003240620h209a0a40ud2063728b5db31a6@mail.gmail.com> <3f0b79eb1003240636y6ba3d739idc4555f88c98e32e@mail.gmail.com> <4BAB5D4E.4000009@enterprisedb.com> Date: Thu, 25 Mar 2010 09:43:53 -0400 Message-ID: <603c8f071003250643k123070f9ufd1dbfca40481c4f@mail.gmail.com> Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL From: Robert Haas To: Heikki Linnakangas Cc: Fujii Masao , Simon Riggs , Aidan Van Dyk , PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.482 tagged_above=-10 required=5 tests=AWL=0.117, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/1009 X-Sequence-Number: 159785 On Thu, Mar 25, 2010 at 8:55 AM, Heikki Linnakangas wrote: > * If a corrupt WAL record is found in archive or streamed from master in > standby mode, throw WARNING instead of PANIC, and keep trying. In > archive recovery (ie. standby_mode=off) it's still a PANIC. We can make > it a WARNING too, which gives the pre-9.0 behavior of starting up the > server on corruption. I prefer PANIC but the discussion is still going on. I don't think we should be changing pre-9.0 behavior more than necessary. ...Robert