[ADMIN] Attempt to re-archive existing WAL logs after restoring from backup

Hello. I've been testing my DB backup and restore procedure and I've run into something I can't figure out. After recovering from a PITR backup, when I do another pg_start_backup PostgreSQL attempts to re-archive the last log again, which fails because it already exists in the archive. I'm ru

Re: [ADMIN] Attempt to re-archive existing WAL logs after restoring from backup

Jon Colverson wrote: I've been testing my DB backup and restore procedure and I've run into something I can't figure out. After recovering from a PITR backup, when I do another pg_start_backup PostgreSQL attempts to re-archive the last log again, which fails because it alread

Re: [ADMIN] Attempt to re-archive existing WAL logs after restoring from backup

Thanks for your reply. Tom Lane wrote: Jon Colverson <[EMAIL PROTECTED]> writes: So, I think the problem is that exitArchiveRecovery() should be marking the restored log file as ".done" (or perhaps not bothering to restore the log file at all?). This looks like a bug to

Re: [ADMIN] Attempt to re-archive existing WAL logs afterrestoringfrom backup

Simon Riggs wrote: I've spent some time re-examining the code and I can't see a route for the discussed problem to occur. All the main code paths do not exhibit this problem in 8.2, so I'm not sure where to go from here. If you can help further, please give me a shout. Thanks a lot for looking