SEO

Hello

We had a strange problem yesterday in one of our servers using PITR
(postgresql 8.1.4).

The script used by archive_command is designed to refuse to overwrite
any pre-existing archive file. Yesterday this situation happened and it
refused to overwrite a file, filling the log file with this error:

-------------------------------------------------
LOG: archive command "archive_wal.sh -P
pg_xlog/000000010000000800000010.0006D5E8.backup -F
000000010000000800000010.0006D5E8.backup" failed: return code 256
WARNING: transaction log file
"000000010000000800000010.0006D5E8.backup" could not be archived: too
many failures
-------------------------------------------------

The problem was that 000000010000000800000010.0006D5E8.backup was
already archived, but under pg_xlog/archive_status/ there were two
files:
-------------------------------------------------
000000010000000800000010.0006D5E8.backup.done
000000010000000800000010.0006D5E8.backup.ready
-------------------------------------------------

so postgresql tryed to archive this file again after the first time. We
deleted the *.backup.ready file and the problem was gone.

This situation should not happen, anyone has seen this problem before?
Ideas?, tips? to find why this happened.

--
Rafael Martinez, <r.m.guerrero@usit.uio.no>
Center for Information Technology Services
University of Oslo, Norway

PGP Public Key: http://folk.uio.no/rafael/


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly