On Mon, 2006-07-10 at 19:34 +0200, Florian G. Pflug wrote:

> This methods seems to work, but it is neither particularly fool-proof nor
> administrator friendly. It's not possible e.g. to reboot the slave without postgres
> abortint the recovery, and therefor processing all wals generated since the last
> backup all over again.

Just submitted a patch to allow restartable recovery, which addresses
this concern.

> Monitoring this system is hard too, since there is no easy way to detect errors
> while restoring a particular wal.

What do you mean?

If there is an ERROR in the WAL file, it stops.
If the restore of the WAL file fails, it retries a few times before
giving up.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match