Thread: Impatient warm standby - Recovery spam in pg_log/startup.log

We're doing a basic WAL shipping replication setup. Our Primary server ships WALs via SCP to the Warm Standby every
fiveminutes. We did the base backup, and brought Warm Standby online. The server ran through all WALs available, but
nowis spamming the startup_log with requests for the next WAL, which hasn't even been generated yet! Is this expected
behavior?If not, how can we stop it? 


cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000042': No such file or directory
LOG:  restored log file "000000010000001300000042" from archive
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory
cp: cannot stat `/home/ubuntu/wals/000000010000001300000043': No such file or directory


Thanks!

That's how I fixed it, by editing the restore_command parameter in
recovery.conf:

restore_command='test -f /var/pgsql/primary-wal-archive/%f && cp
/var/pgsql/primary-wal-archive/%f %p'

Basically, it's testing for the existence of the file before trying to copy
it.



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Impatient-warm-standby-Recovery-spam-in-pg-log-startup-log-tp5713094p5721039.html
Sent from the PostgreSQL - novice mailing list archive at Nabble.com.