Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 4AFBE6354E1 for ; Wed, 13 May 2009 18:05:48 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 56658-02 for ; Wed, 13 May 2009 18:05:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137138.authsmtp.net (outmail137138.authsmtp.net [62.13.137.138]) by mail.postgresql.org (Postfix) with ESMTP id AAB63636644 for ; Wed, 13 May 2009 18:01:40 -0300 (ADT) Received: from mail-c188.authsmtp.com (mail-c188.authsmtp.com [62.13.128.25]) by punt10.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4DL1WAu021982; Wed, 13 May 2009 22:01:32 +0100 (BST) Received: from [192.168.0.2] (85-211-96-202.dyn.gotadsl.co.uk [85.211.96.202]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4DL1Uu0037920; Wed, 13 May 2009 22:01:31 +0100 (BST) Subject: Re: New trigger option of pg_standby From: Simon Riggs To: Tom Lane Cc: Heikki Linnakangas , Fujii Masao , Guillaume Smet , Peter Eisentraut , Kevin Grittner , pgsql-hackers In-Reply-To: <18106.1242247646@sss.pgh.pa.us> References: <3f0b79eb0903242329j12865d55s348f5c873a956e71@mail.gmail.com> <1239381103.16396.30.camel@ebony.2ndQuadrant> <3f0b79eb0904122252t1f4c5860v919d199f399ccf72@mail.gmail.com> <3f0b79eb0904132241p18084914g792cb8e5ab3eebb3@mail.gmail.com> <3f0b79eb0904150101pb1c59a3ubb422867e8e6a944@mail.gmail.com> <49EE1E3F.9050307@enterprisedb.com> <3f0b79eb0904212209i7fbd8b68k71db1fef09c62751@mail.gmail.com> <49F01D79.8020805@enterprisedb.com> <3f0b79eb0904230515p751b5248n6ef96880617db055@mail.gmail.com> <4A095A39.3030100@enterprisedb.com> <3f0b79eb0905130127u3a3275b1w79f4d8cb729ded36@mail.gmail.com> <4A0A86D2.9080602@enterprisedb.com> <1985.1242234105@sss.pgh.pa.us> <4A0B10C7.2040309@enterprisedb.com> <1242247404.3843.503.camel@ebony.2ndQuadrant> <18106.1242247646@sss.pgh.pa.us> Content-Type: text/plain Date: Wed, 13 May 2009 22:04:06 +0100 Message-Id: <1242248646.3843.511.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 3c9b1c73-4001-11de-aecc-001871e930f4 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksacRtFaQZbYFhI HGQLW11EUl97WWJ/ aAgfZQBDYEtPQQxs TkpJQE1QEQdtHhxP WBpqLhgXMgVGe3l5 Z0YsXHBZXAp5Jk8v Qx1TFnACZWdhdWEe BBVFJlYHIx5Kfh5N bVEqXXANN2FJBC9q VzwTFhsSEA9kHWxz Tx5FMUgTTkkGBHY7 XwwDGjNnGkNNXyoE NAAvLFIWDS41 X-Authentic-SMTP: 61633235383639.cat.dmpriest.net.uk:1562/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse 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=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200905/598 X-Sequence-Number: 138140 On Wed, 2009-05-13 at 16:47 -0400, Tom Lane wrote: > Simon Riggs writes: > > recovery_end_command is performed *after* the UpdateControlFile() once > > the we are DB_IN_PRODUCTION. > > Hmm, shouldn't it be after the last checkpoint Definitely. > but before we go to DB_IN_PRODUCTION? I think it can be either, so I'll go with your proposal. (I'm aware Fujii-san is asleep right now, so we should expect another viewpoint before tomorrow). -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support