Subject: Re: Re: [COMMITTERS] pgsql: Make standby server
	continuously retry 	restoring the next WAL
From: Simon Riggs <simon@2ndQuadrant.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Dimitri Fontaine <dfontaine@hi-media.com>,
	Fujii Masao <masao.fujii@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
In-Reply-To: <4B740C6C.3010607@enterprisedb.com>
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>
	<4B740C6C.3010607@enterprisedb.com>
Content-Type: text/plain
Date: Thu, 11 Feb 2010 14:17:14 +0000
Message-Id: <1265897834.7341.1714.camel@ebony>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Thu, 2010-02-11 at 15:55 +0200, Heikki Linnakangas wrote:
> 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.

So we still need a script but it can't be pg_standby? Hmmm, OK...

Might it not be simpler to add a parameter onto pg_standby?
We send %s to tell pg_standby the standby_mode of the server which is
calling it so it can decide how to act in each case.

-- 
 Simon Riggs           www.2ndQuadrant.com