Message-ID: <4B740C6C.3010607@enterprisedb.com>
Date: Thu, 11 Feb 2010 15:55:56 +0200
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Organization: EnterpriseDB
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706)
MIME-Version: 1.0
To: Simon Riggs <simon@2ndQuadrant.com>
CC: Dimitri Fontaine <dfontaine@hi-media.com>,
	Fujii Masao <masao.fujii@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously
	retry 	restoring the next WAL
References: <20100127152751.3B2047541B9@cvs.postgresql.org>	
	<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>	
	<877hqjc2kk.fsf@hi-media-techno.com>
	<1265896250.7341.1627.camel@ebony>
In-Reply-To: <1265896250.7341.1627.camel@ebony>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Simon Riggs wrote:
> One question then: how do we ensure that the archive does not grow too
> big? pg_standby cleans down the archive using %R. That function appears
> to not exist anymore. 

You can still use %R. Of course, plain 'cp' won't know what to do with
it, so a script will then be required. We should probably provide a
sample of that in the docs, or even a ready-made tool similar to
pg_standby but without the waiting.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com