Re: [HACKERS] Warm-Standby using WAL archiving / Seperate

2006-07-11 Thread Andrew Rawnsley
Just having a standby mode that survived shutdown/startup would be a nice start... I also do the blocking-restore-command technique, which although workable, has a bit of a house-of-cards feel to it sometimes. On 7/10/06 5:40 PM, Florian G. Pflug [EMAIL PROTECTED] wrote: Merlin Moncure

Re: [HACKERS] Warm-Standby using WAL archiving / Seperate

2006-07-11 Thread Simon Riggs
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

Re: [HACKERS] Warm-Standby using WAL archiving / Seperate

2006-07-11 Thread Hannu Krosing
Ühel kenal päeval, T, 2006-07-11 kell 08:38, kirjutas Andrew Rawnsley: Just having a standby mode that survived shutdown/startup would be a nice start... I think that Simon Riggs did some work on this at the code sprint yesterday. I also do the blocking-restore-command technique, which

Re: [HACKERS] Warm-Standby using WAL archiving / Seperate pg_restorelog application

2006-07-10 Thread Merlin Moncure
On 7/10/06, Florian G. Pflug [EMAIL PROTECTED] 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

Re: [HACKERS] Warm-Standby using WAL archiving / Seperate pg_restorelog

2006-07-10 Thread Florian G. Pflug
Merlin Moncure wrote: On 7/10/06, Florian G. Pflug [EMAIL PROTECTED] 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