Re: Backup history file should be replicated in Streaming Replication?

Florian Pflug <fgp.phlo.org@gmail.com>

From: Florian Pflug <fgp.phlo.org@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2009-12-18T17:22:34Z
Lists: pgsql-hackers
On 18.12.09 17:05 , Robert Haas wrote:
> On Fri, Dec 18, 2009 at 11:03 AM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com>  wrote:
>> Or some way for to register the standby with the master so that
>> the master knows it's out there, and still needs the logs, even when
>> it's not connected.
>
> That is the real answer, I think.

It'd prefer if the slave could automatically fetch a new base backup if 
it falls behind too far to catch up with the available logs. That way, 
old logs don't start piling up on the server if a slave goes offline for 
a long time.

The slave could for example run a configurable shell script in that 
case, for example. You could then use that to rsync the data directory 
from the server (after a pg_start_backup() of course).

best regards,
Florian Pflug