Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 95B2B635109 for ; Thu, 11 Feb 2010 14:14:44 -0400 (AST) 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 93239-02 for ; Thu, 11 Feb 2010 18:14:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail136059.authsmtp.com (outmail136059.authsmtp.com [62.13.136.59]) by mail.postgresql.org (Postfix) with ESMTP id 97A5A6335C9 for ; Thu, 11 Feb 2010 14:14:28 -0400 (AST) Received: from mail-c194.authsmtp.com (mail-c194.authsmtp.com [62.13.128.121]) by punt7.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id o1BIEJZ9006757; Thu, 11 Feb 2010 18:14:19 GMT Received: from [192.168.1.8] (c-68-33-3-167.hsd1.md.comcast.net [68.33.3.167]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id o1BIEEvq088069; Thu, 11 Feb 2010 18:14:14 GMT Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL From: Simon Riggs To: Tom Lane Cc: Heikki Linnakangas , Aidan Van Dyk , Fujii Masao , PostgreSQL-development In-Reply-To: <11741.1265911704@sss.pgh.pa.us> References: <3f0b79eb1002092105r21e009d3v468496058ba04392@mail.gmail.com> <4B726120.80007@enterprisedb.com> <1265884657.7341.1192.camel@ebony> <4B73F678.8070109@enterprisedb.com> <1265891248.7341.1346.camel@ebony> <4B73FB99.4080403@enterprisedb.com> <1265893599.7341.1454.camel@ebony> <4B740613.5090004@enterprisedb.com> <20100211140118.GB14128@oak.highrise.ca> <4B74118C.30704@enterprisedb.com> <20100211144204.GC14128@oak.highrise.ca> <4B7438A9.8090902@enterprisedb.com> <11741.1265911704@sss.pgh.pa.us> Content-Type: text/plain Date: Thu, 11 Feb 2010 18:14:12 +0000 Message-Id: <1265912052.7341.2276.camel@ebony> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-Server-Quench: 43739750-1739-11df-80b9-0022640b883e X-Report-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCdxZQATClZOTQEd DAteCiN5VAwpPBRK HVkIKg5MJUcNSQVJ NksacxtFaQRba1xT HGQLWlREUVV7WGd/ ag8faw1DYUlQXBtr Vk9WR1pVCwUmXh1z f2trFFhyfw1Gfnc+ bUBhXj5fX0N5fEF4 QlNVEm4PeGZhPDYC WEAKfh5UcAFIeBtF OFh3VyZDAzANdhEY NiQQEgoKCH1lJXYd cSoqCHczfXomJAUJ DwgNBiwrTwUgTiY+ Zwc6I1gQFldZKUgo L1Y7OxoTNBkOCwtD GFxWBD4RPVQdXTtj Fw5BQUkEETtSCTtc D1UuLw9USgN7fkIA X-Authentic-SMTP: 61633235383639.1015:706/Kp X-AuthFastPath: 255 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=-1.855 tagged_above=-10 required=5 tests=AWL=0.745, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/911 X-Sequence-Number: 157254 On Thu, 2010-02-11 at 13:08 -0500, Tom Lane wrote: > Heikki Linnakangas writes: > > -1. it isn't necessary for PITR. It's a new requirement for > > standby_mode='on', unless we add the file size check into the backend. I > > think we should add the file size check to the backend instead and save > > admins the headache. > > I think the file size check needs to be in the backend purely on safety > grounds. Whether we make pg_standby useful for this context is a > different discussion. Happy with that. -- Simon Riggs www.2ndQuadrant.com