Re: [HACKERS] [GENERAL] 8.1.4 - problem with PITR - .backup.done / backup.ready version of the same file at the same time.

2006-05-30 Thread Tom Lane
Rafael Martinez, Guerrero [EMAIL PROTECTED] writes: The problem was that 000100080010.0006D5E8.backup was already archived, but under pg_xlog/archive_status/ there were two files: - 000100080010.0006D5E8.backup.done

Re: [HACKERS] [GENERAL] 8.1.4 - problem with PITR - .backup.done /

2006-05-30 Thread Rafael Martinez
On Tue, 2006-05-30 at 09:45 -0400, Tom Lane wrote: Rafael Martinez, Guerrero [EMAIL PROTECTED] writes: The problem was that 000100080010.0006D5E8.backup was already archived, but under pg_xlog/archive_status/ there were two files:

Re: [HACKERS] [GENERAL] 8.1.4 - problem with PITR - .backup.done / backup.ready version of the same file at the same time.

2006-05-30 Thread Tom Lane
Rafael Martinez [EMAIL PROTECTED] writes: What happens if we have a race condition and the archiver creates a .done file between the last check for the .done file and the creation of the .ready file by XLogArchiveNotify? That can't happen; the archiver creates the .done file by rename()ing the

Re: [HACKERS] [GENERAL] 8.1.4 - problem with PITR - .backup.done /

2006-05-30 Thread Rafael Martinez
On Tue, 2006-05-30 at 15:38 -0400, Tom Lane wrote: [...] My thought is that the stat()s on the .done file failed for some obscure reason, perhaps insufficient kernel resources, even though the file was actually there. If you have postmaster log output for the interval in which this