Colin Wilson <cwilson@xxxxxxxxxxxxxxxxxxxxx> wrote: > Once the server was back up we noticed the xlog file it was > looking for was one that the logs say was already applied. It > was 7 xlogs back to be exact. It is not unusual for WAL replay to ask for files out of order or multiple times in certain circumstances. A standby could never hope to keep up with a busy master if it waited for a disk flush on every WAL file before requesting the next, so recovery is one of those times where it has to go back and ask for files containing data which wasn't flushed to disk. > We have our log shipping target replay the xlogs and then delete > them when it is done Not a good idea. > how to get the system to start applying the logs we have? Since you don't know how much of what it applied the first time actually made it to disk, I wouldn't trust any recovery attempt. Time to grab a new base backup from the master, I think. And fix that script to not delete. Personally, I like to keep the last two base backups and all the WAL files needed to restore from the earlier of those forward. We have cleanup script that deletes the oldest backup and WAL files only needed for recovery from it when we receive a new one. -Kevin -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
