Re: [HACKERS] Warm Standby restore_command documentation

2009-04-20 Thread Andreas Pflug
Heikki Linnakangas wrote: > Andreas Pflug wrote: >> I've been following the thread with growing lack of understanding why >> this is so hardly discussed, and I went back to the documentation of >> what the restore_command should do ( >> http://www.postgresql.org/docs/8.3/static/warm-standby.html )

Re: [HACKERS] Warm Standby restore_command documentation

2009-04-20 Thread Heikki Linnakangas
Andreas Pflug wrote: I've been following the thread with growing lack of understanding why this is so hardly discussed, and I went back to the documentation of what the restore_command should do ( http://www.postgresql.org/docs/8.3/static/warm-standby.html ) While the algorithm presented in the

Re: [HACKERS] Warm Standby restore_command documentation (was: New trigger option of pg_standby)

2009-04-14 Thread Fujii Masao
Hi, On Wed, Apr 15, 2009 at 3:30 AM, Andreas Pflug wrote: > I've been following the thread with growing lack of understanding why > this is so hardly discussed, and I went back to the documentation of > what the restore_command should do ( > http://www.postgresql.org/docs/8.3/static/warm-standby.

[HACKERS] Warm Standby restore_command documentation (was: New trigger option of pg_standby)

2009-04-14 Thread Andreas Pflug
I've been following the thread with growing lack of understanding why this is so hardly discussed, and I went back to the documentation of what the restore_command should do ( http://www.postgresql.org/docs/8.3/static/warm-standby.html ) While the algorithm presented in the pseudocode isn't dealin