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

Re: BUG #2488: backup history file is archived doubly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Masao Fujii" <fujii(dot)masao(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2488: backup history file is archived doubly
Date: 2006-06-22 18:46:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"Masao Fujii" <fujii(dot)masao(at)oss(dot)ntt(dot)co(dot)jp> writes:
> The cause of the problem is that pg_stop_backup creates two *.ready files.
> One file is created by pg_stop_backup > RemoveOldBackupHistory >
> XLogArchiveIsDone > XLogArchiveNotify.
> Another is created by pg_stop_backup > XLogArchiveNotify.

Oooh, good catch.  The cleanest solution would be to modify
RemoveOldBackupHistory so that it explicitly skips the current entry.
But I'm strongly tempted to just remove the code in pg_stop_backup,
and document that RemoveOldBackupHistory gets the job done (perhaps
renaming it).

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: EresmasDate: 2006-06-22 19:50:26
Subject: Re: BUG #2487: Immutable functions results
Previous:From: Tom LaneDate: 2006-06-22 17:41:32
Subject: Re: BUG #2490: '||' and type casting for user defined types

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