Re: Time-Delayed Standbys

(2013/12/09 19:36), KONDO Mitsumasa wrote:
> * Problem 1
> I read your wittened document. There is "PITR has not affected".
> However, when I run PITR with min_standby_apply_delay=3000000, it cannot start
> server. The log is under following.
>> [mitsu-ko@localhost postgresql]$ bin/pg_ctl -D data2 start
>> server starting
>> [mitsu-ko@localhost postgresql]$ LOG:  database system was interrupted; last
>> known up at 2013-12-08 18:57:00 JST
>> LOG:  creating missing WAL directory "pg_xlog/archive_status"
>> cp: cannot stat `../arc/00000002.history':
>> LOG:  starting archive recovery
>> LOG:  restored log file "000000010000000000000041" from archive
>> LOG:  redo starts at 0/41000028
>> LOG:  consistent recovery state reached at 0/410000F0
>> LOG:  database system is ready to accept read only connections
>> LOG:  restored log file "000000010000000000000042" from archive
>> FATAL:  cannot wait on a latch owned by another process
>> LOG:  startup process (PID 30501) exited with exit code 1
>> LOG:  terminating any other active server processes
> We need recovery flag for controling PITR situation.
Add my comment. We have to consider three situations.

1. PITR
2. replication standby
3. replication standby with restore_command

I think this patch cannot delay in 1 situation. So I think you should add only 
StandbyModeRequested flag in conditional branch.

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center