Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 39DCE64FCFE for ; Wed, 22 Oct 2008 18:28:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 45712-05 for ; Wed, 22 Oct 2008 18:28:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137080.authsmtp.com (outmail137080.authsmtp.com [62.13.137.80]) by postgresql.org (Postfix) with ESMTP id 476C364FCFD for ; Wed, 22 Oct 2008 18:28:04 -0300 (ADT) Received: from mail-c189.authsmtp.com (mail-c189.authsmtp.com [62.13.128.71]) by punt4.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id m9MLRcbH004534; Wed, 22 Oct 2008 22:27:38 +0100 (BST) Received: from [192.168.0.3] (85-211-100-20.dyn.gotadsl.co.uk [85.211.100.20]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id m9MLRbut060294; Wed, 22 Oct 2008 22:27:37 +0100 (BST) Subject: Re: Another PITR question From: Simon Riggs To: Alvaro Herrera Cc: Scott Whitney , pgsql-admin@postgresql.org In-Reply-To: <20081022200919.GE4022@alvh.no-ip.org> References: <20081022200650.4F5717E424E@mail.int.journyx.com> <20081022200919.GE4022@alvh.no-ip.org> Content-Type: text/plain Date: Wed, 22 Oct 2008 22:30:24 +0100 Message-Id: <1224711024.27145.505.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 3ffaca42-a080-11dd-bc7a-001f29070be2 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksadRtFagdbYlpF HGQLW1xEUl97W2R/ aAIfZQBDYEtPQQRq UFZLQk1QEQdtHhxP WxdjLnsgMkFGfn5y bEIsX3VbXQp5IxAs ER9QF3BXZW9gdWEe BBRFJVBTIR5Kfh4T aFl/U3NfNGdJBC9q VzwaExUQGwAXASJS XgEANxoqYHoxVich SgseHDIpdXJf X-Authentic-SMTP: 61633235383639.kestrel.dmpriest.net.uk:1378/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: 200810/157 X-Sequence-Number: 30613 On Wed, 2008-10-22 at 17:09 -0300, Alvaro Herrera wrote: > Scott Whitney wrote: > > > However, I want the standby to CONSTANTLY stay in recovery mode, not > > just restore the WALs it finds when I start it. > > > > Is this possible? Can someone explain or point me to some example docs > > somewhere? > > http://www.postgresql.org/docs/8.3/static/pgstandby.html We should backpatch the docs for 8.2 also. I know we don't usually do that but it would save some time for people. Or at least allow comments to be added to previous doc versions. 8.3 docs have the wording "A working example of a waiting restore_command is provided as a contrib module named pg_standby. It should be used as a reference on how to correctly implement the logic described above. It can also be extended as needed to support specific configurations or environments." -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support