Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 22 Jun 2006 14:46:56 -0400
"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
- References:
- BUG #2488: backup history file is archived doubly
- From: Masao Fujii
- BUG #2488: backup history file is archived doubly
- Prev by Date: Re: BUG #2490: '||' and type casting for user defined types
- Next by Date: Re: BUG #2487: Immutable functions results
- Previous by thread: BUG #2488: backup history file is archived doubly
- Next by thread: BUG #2489: Metadata dosen't match tables
- Indexes: