* Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> [100210 02:33]: > Hmm, so after running restore_command, check the file size and if it's > too short, treat it the same as if restore_command returned non-zero? > And it will be retried on the next iteration. Works for me, though OTOH > it will then fail to complain about a genuinely WAL file that's > truncated for some reason. I guess there's no way around that, even if > you have a script as restore_command that does the file size check, it > will have the same problem.
But isn't this something every current PITR archive already "works around"... Everybody doing PITR archives already know the importance of making the *appearance* of the WAL filename in the archive atomic. Don't docs warn about plain cp not being atomic and allowing "short" files to appear in the archive... I'm not sure why "streaming recovery" suddenly changes the requirements... a. -- Aidan Van Dyk Create like a god, ai...@highrise.ca command like a king, http://www.highrise.ca/ work like a slave.
signature.asc
Description: Digital signature
