Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Rafael Martinez, Guerrero" <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [GENERAL] 8.1.4 - problem with PITR - .backup.done / backup.ready version of the same file at the same time.
Date: 2006-05-30 13:45:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
"Rafael Martinez, Guerrero" <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> writes:
> 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
> -------------------------------------------------

> This situation should not happen, anyone has seen this problem before?

No, it shouldn't.  What I suspect is that XLogArchiveIsDone() got
confused and created a duplicate .ready file.  It basically assumes
that the only way its stat() calls can fail is ENOENT, ie, file not
there ... but I wonder if they failed for some other reason instead.
What sort of platform and filesystem is this on?

Did you happen to make note of the mod times of the two files before
deleting them?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-05-30 14:01:49
Subject: Re: [PATCH] Improve EXPLAIN ANALYZE overhead by sampling
Previous:From: Andrew DunstanDate: 2006-05-30 13:41:59
Subject: Re: plperl's ppport.h out of date?

pgsql-general by date

Next:From: Tatsuo IshiiDate: 2006-05-30 13:48:38
Subject: Re: Charset conversion error
Previous:From: Lars HaugsethDate: 2006-05-30 13:39:48
Subject: Compound words giving undesirable results with tsearch2

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group