Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 274F7633E53 for ; Fri, 2 Oct 2009 06:10: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 70788-01 for ; Fri, 2 Oct 2009 09:10:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail136008.authsmtp.com (outmail136008.authsmtp.com [62.13.136.8]) by mail.postgresql.org (Postfix) with ESMTP id E29126352CC for ; Fri, 2 Oct 2009 06:10:15 -0300 (ADT) Received: from mail-c194.authsmtp.com (mail-c194.authsmtp.com [62.13.128.121]) by punt3.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n929ABd3083082; Fri, 2 Oct 2009 10:10:11 +0100 (BST) Received: from [192.168.0.5] (88-110-190-77.dynamic.dsl.as9105.com [88.110.190.77]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n929A86Y055180; Fri, 2 Oct 2009 10:10:08 +0100 (BST) Subject: Re: Hot Standby on git From: Simon Riggs To: Heikki Linnakangas Cc: pgsql-hackers In-Reply-To: <4AC5B92A.7090508@enterprisedb.com> References: <1253958559.4449.833.camel@ebony.2ndQuadrant> <4AC2FBB9.7060304@enterprisedb.com> <1254408330.17864.233.camel@ebony.2ndQuadrant> <4AC4CF18.50309@enterprisedb.com> <1254413624.17864.243.camel@ebony.2ndQuadrant> <4AC5A60F.5050503@enterprisedb.com> <1254468966.17864.301.camel@ebony.2ndQuadrant> <4AC5AF36.3020900@enterprisedb.com> <1254470874.17864.309.camel@ebony.2ndQuadrant> <4AC5B92A.7090508@enterprisedb.com> Content-Type: text/plain Date: Fri, 02 Oct 2009 10:13:43 +0100 Message-Id: <1254474823.17864.326.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 61b32ccd-af33-11de-9488-0022640b883e X-Report-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCdxZQATClZOTQEd DAteCiN5VAwpPBRK HVkIKg5MJUcNSQVJ NksadBtFaAdbYlpF HGQLW11EUV17WGN/ awIfZQ1DY0tOQQRj UFZORU1QEQdtHhxP WBccW2h6cWxGfXtx bUYsXXNZWgp8dBR+ QB0HQXBXM2RjdWEe BBVFfgdceB5Kfh1H bFR/BnsFYjBJBC9q VzwTFhsSEA9kHWx1 RR1FFk4bR0oBD3Y7 QVgNHClH X-Authentic-SMTP: 61633235383639.1015:706/Kp X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.582 tagged_above=-10 required=5 tests=AWL=0.017, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200910/145 X-Sequence-Number: 146957 On Fri, 2009-10-02 at 11:26 +0300, Heikki Linnakangas wrote: > Simon Riggs wrote: > > On Fri, 2009-10-02 at 10:43 +0300, Heikki Linnakangas wrote: > > > >> It seems dangerous to write a WAL record after the shutdown checkpoint. > >> It will be overwritten by subsequent startup, which is a recipe for trouble. > > > > I've said its a corner case and not worth spending time on. I'm putting > > it in at your request. If it's not correct before and not correct after, > > where exactly do you want it? > > I don't know. Perhaps it should go between the REDO pointer of the > shutdown checkpoint and the checkpoint record itself. That would seem minimally invasive approach and would appear to work for both cases. Will do. -- Simon Riggs www.2ndQuadrant.com