Re: pg_standby and build farm

Hi all,<br /> I'm new to the forums, so bear with me on my questions. I've set up an auto-archive and auto-recover
pairof databases using pg_standby, which I'm prototyping various products for high availability. I've noticed that when
Iattempt to fail from the primary archiver to the secondary recovery db using the pg_standby trigger file, the
secondarydetects the trigger file, flags that it couldn't read the current WAL file pg_standby was waiting on, then
attemptsto read in the previous WAL file. I use the -m option in pg_standby, so the previous WAL file no longer exists,
whichcauses the secondary postgres to "panic" on not being able to open the previous WAL and terminates. Is there a way
toprevent the looking for the previous, or preserving the previous WAL file so that when the trigger file is detected,
thesecondary will come all the way up, completely its recovery mode? <br /><br /> Thanks,<br /> Doug Knight