At Wed, 16 Jun 2021 12:04:03 +0900 (JST), Kyotaro Horiguchi <horikyota....@gmail.com> wrote in > Ok, if we follow the direction that we are responsible for ensuring > that every user has reliable backups, I don't come up with proper > description about that. > > We could list several "requirement" like "do sync after copy", "take a > checksum for all files then check it periodically" or other things but > what is more important things to list here, I think, is "how we run > the archive_command". > > Doesn't the following work for now? > > (No example) > > - "%f is replace by ... %p is .., %r is ... in archive_command" > > - We call the archive_command for every wal segment which is finished. > > - We may call the archive_command for the same file more than once. > > - We may call the archive_command for different files with the same > name. In this case server is working incorrectly and need a > check. Don't overwrite with the new content. > > - We don't offer any durability or integrity on the archived > files. All of them is up to you. You can use some existing > solutions for archiving. See the following links.
Of course, there should be some descriptions about error handling along with. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
