Andy Shellam <andy.shellam@xxxxxxxxxxxxxxxxx> writes: > Note there are plenty more files ready to run in the archive, and the > contents of the backup label only mention 1A as the final WAL file of > the backup, so it is starting to read the next WAL file, but stopping > for some reason. Is it because of the "record with zero length" that's > causing it to fail? Yes --- that indicates the end of archive. It sounds to me like file 1B was archived while still only partly filled. Check the process you're using for deciding when to copy WAL files. > Also why is it restoring 1B from the archive twice? I think that's expected behavior --- it has something to do with wanting to make the copy of 1B into the new writable front WAL segment. You can dig through xlog.c if you want the details. regards, tom lane
