From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Wierd quirk of HS/SR, probably not fixable |
Date: | 2010-04-27 19:12:02 |
Message-ID: | 4BD73702.8040409@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
> 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.
Oh, the backup history file. We stopped relying on that with the
introduction of the end-of-backup record, to make life easier for
streaming replication, and because it's simpler anyway. I don't think we
should go back to it.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-04-27 19:20:30 | Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct |
Previous Message | Heikki Linnakangas | 2010-04-27 19:00:04 | Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct |