RE: Re: Hot to restore repo from hot-backup.py

This is usually the case with most ACID stores. Just because a
transaction's commit() has returned successfully just means that the
data has been inserted into the transaction log. It doesn't guarantee
that the data has been inserted into the main database file yet.

Bill

----
Do you want a dangerous fugitive staying in your flat?
No.
Well, don't upset him and he'll be a nice fugitive staying in your flat.
 
> -----Original Message-----
> From: mark benedetto king [mailto:bking@inquira.com]
> Sent: Wednesday, July 17, 2002 4:40 PM
> To: Ben Collins-Sussman
> Cc: Eric Gillespie; dev@subversion.tigris.org
> Subject: Re: Hot to restore repo from hot-backup.py
> 
> On Wed, Jul 17, 2002 at 05:36:43PM -0500, Ben Collins-Sussman wrote:
> > But it seems that your backup had unplayed transactions in it, which
I
> > don't get.  Can someone more knowledgable explain?  Perhaps
> > Mr. Bostic?  :-)
> >
> 
> Well, I'm not nearly as authoritative as Mr. Bostic but wouldn't it
> make sense that a transaction can be considered complete as soon as
> the log is stabilized and the in-memory datastructures are updated
> (but before then on-disk database is updated)?
> 
> --ben
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org