Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 06802633962 for ; Tue, 12 May 2009 08:25:12 -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 12535-09 for ; Tue, 12 May 2009 08:25:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail128094.authsmtp.com (outmail128094.authsmtp.com [62.13.128.94]) by mail.postgresql.org (Postfix) with ESMTP id 6D94D633957 for ; Tue, 12 May 2009 08:24:49 -0300 (ADT) Received: from mail-c193.authsmtp.com (mail-c193.authsmtp.com [62.13.128.118]) by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4CBOaBc005702; Tue, 12 May 2009 12:24:36 +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 n4CBOWLn087261; Tue, 12 May 2009 12:24:33 +0100 (BST) Subject: Re: New trigger option of pg_standby From: Simon Riggs To: Heikki Linnakangas Cc: Fujii Masao , Guillaume Smet , Tom Lane , Peter Eisentraut , Kevin Grittner , pgsql-hackers In-Reply-To: <4A095A39.3030100@enterprisedb.com> References: <3f0b79eb0903242329j12865d55s348f5c873a956e71@mail.gmail.com> <49DDEE72.6030803@enterprisedb.com> <3f0b79eb0904092047w355e0b3ar527a9285b161ef91@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> Content-Type: text/plain Date: Tue, 12 May 2009 12:27:03 +0100 Message-Id: <1242127623.3843.237.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 78b1c1a1-3ee7-11de-8a51-002264978518 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksacRtFaQdbYFhI HGQLW11EUV97W2d/ aA8fZQBDYEtPQQxs TkpJQE1QEQdtHhxP WBptIGYVC1tGcHly Y0csXHBcWAp9fRR8 EU8FFHAFMDJndWEe BBVFf1JRcR5Kfh1H bFR2U3sIYG1JBC9q VzwTFhsSEA9kHWxz Tx5FMUgTTkkGBHY7 XwwDGjNnGkNNXyoE NAAvLFIWDS41 X-Authentic-SMTP: 61633235383639.pelican.dmpriest.net.uk:1562/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.052 tagged_above=0 required=5 tests=AWL=0.052 X-Spam-Level: X-Archive-Number: 200905/538 X-Sequence-Number: 138080 On Tue, 2009-05-12 at 14:15 +0300, Heikki Linnakangas wrote: > Here's another idea: Let's modify xlog.c so that when the server asks > for WAL file X, and restore_command returns "not found", the server > will not ask for any WAL files >= X again (in that recovery session). > Presumably if X doesn't exist, no later files will exist either. That was proposed and rejected earlier, though not in this context. Sounds fine to me. I agree that we should simplify/clarify the file request pattern, which is the source of many difficulties over last few years. I would further propose that I take pg_standby out as a module, so we can more easily support earlier releases. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support