Re: Wierd quirk of HS/SR, probably not fixable - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Wierd quirk of HS/SR, probably not fixable
Date
Msg-id 1272392079.4161.7886.camel@ebony
Whole thread Raw
In response to Re: Wierd quirk of HS/SR, probably not fixable  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Wierd quirk of HS/SR, probably not fixable  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, 2010-04-27 at 20:14 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > On Tue, 2010-04-27 at 18:13 +0300, Heikki Linnakangas wrote:
> >> Simon Riggs wrote:
> >>> If pg_stop_backup() is run it creates the .backup file in the archive.
> >>> In the absence of that file, we should be able to work out that
> >>> pg_stop_backup() was not run. 
> >> It's just as likely that the file is there even though the backup didn't
> >> finish, though.
> > 
> > It's possible, but not likely. It would need to break at a very specific
> > place for that to be the case. Whereas the test I explained would work
> > for about 99% of the time between start and stop backup, except for the
> > caveat I explained also.
> 
> I don't understand how you arrived at that figure. 

You're talking about the backup_label file, I'm talking about
the .backup file in the archive.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: testing HS/SR - 1 vs 2 performance
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct