Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 42175632B60 for ; Fri, 2 Oct 2009 04:32:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 54617-07 for ; Fri, 2 Oct 2009 07:32:14 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by mail.postgresql.org (Postfix) with SMTP id EADA4632B3B for ; Fri, 2 Oct 2009 04:32:16 -0300 (ADT) Received: from source ([209.85.219.214]) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKSsWsf5RfJxL+sGJDwX8EUTaWzkEg7V22@postini.com; Fri, 02 Oct 2009 00:32:17 PDT Received: by ewy10 with SMTP id 10so724196ewy.33 for ; Fri, 02 Oct 2009 00:32:14 -0700 (PDT) Received: by 10.211.146.17 with SMTP id y17mr402695ebn.43.1254468734432; Fri, 02 Oct 2009 00:32:14 -0700 (PDT) Received: from ?192.168.1.117? ([88.195.103.165]) by mx.google.com with ESMTPS id 10sm1360950eyd.37.2009.10.02.00.32.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Oct 2009 00:32:13 -0700 (PDT) Message-ID: <4AC5AC7A.8070801@enterprisedb.com> Date: Fri, 02 Oct 2009 10:32:10 +0300 From: Heikki Linnakangas Organization: EnterpriseDB User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: Simon Riggs CC: pgsql-hackers Subject: Re: Hot Standby on git References: <1253958559.4449.833.camel@ebony.2ndQuadrant> <4AC37D2D.9060400@enterprisedb.com> <1254406060.17864.219.camel@ebony.2ndQuadrant> In-Reply-To: <1254406060.17864.219.camel@ebony.2ndQuadrant> 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=-2.443 tagged_above=-10 required=5 tests=AWL=0.156, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200910/138 X-Sequence-Number: 146950 Simon Riggs wrote: > I will docuemnt the recommendation to set max_standby_delay = 0 if > performing an archive recovery (and explain why). Hmm, not sure if that's such a good piece of advice either. It will mean waiting for queries forever, which probably isn't what you want if you're performing archive recovery. Or maybe it is? Maybe -1? I guess it depends on the situation... -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com