| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
| Cc: | Postgresql-General <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Warm-Standby using WAL archiving / Seperate |
| Date: | 2006-07-11 20:33:55 |
| Message-ID: | 1152650036.2465.79.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-07-11 20:35:19 | Re: Three weeks left until feature freeze |
| Previous Message | Stephen Frost | 2006-07-11 20:33:18 | Re: Three weeks left until feature freeze |