8.1.4 - problem with PITR - .backup.done / backup.ready version of the same file at the same time.

From: "Rafael Martinez, Guerrero" <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
To: pgsql-general(at)postgresql(dot)org
Subject: 8.1.4 - problem with PITR - .backup.done / backup.ready version of the same file at the same time.
Date: 2006-05-30 10:48:02
Message-ID: 1148986082.5620.493.camel@bbking.uio.no
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
Center for Information Technology Services
University of Oslo, Norway

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eci Souji 2006-05-30 10:48:43 Re: DB structure for logically similar objects in different
Previous Message Tino Wildenhain 2006-05-30 10:35:34 Re: R: [ODBC] information request on postgresql --> oracle

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-05-30 12:03:20 Re: PL/PGSQL: Dynamic Record Introspection
Previous Message Marko Kreen 2006-05-30 07:44:31 Re: Inefficient bytea escaping?