On Wed, Jan 12, 2011 at 3:48 PM, Richard Hipp <[email protected]> wrote:
> On Wed, Jan 12, 2011 at 5:27 AM, Max Vlasov <[email protected]> wrote: > > > On Thu, Dec 23, 2010 at 3:10 PM, Max Vlasov <[email protected]> > wrote: > > > > > Hi, > > > I experimented with artificial power loss (using hd box) and 3.7.4 both > > > library and shell didn't restore the files to the initial state. 3.6.10 > > > restores successfully. > > > > > > > > > This is a kind of repost, there wasn't any answer for my initial one. > > Please > > let me know is this bug or not a bug, I can't sleep without knowing the > > truth :) > > > > > The journal file is "stale". It is not a "hot journal". And it won't (and > can't) be rolled back. It's just a junk file that got left around. It > will > get cleaned up on the next write transaction. I guess you are asking for > an > enhancement for it to be cleaned up on the next read transaction. > > Richard, thanks for the clarification, it was just a little strange that previous versions (at least 3.6.10 I mentioned) deletes the same journal file upon simple opening (no writing) so possibly something was introduced after that made things a little more complex as you described. Also generally speaking the presence of -journal always was a kind of visual indication that either a write operation in progress (if connection is live) or something ended unexpectedly on previous session (if it's closed), but it appears that currently even several read-only sessions after that can keep this file around for a long period of time and this logic no longer works. Anyway I can live with that (and also sleep:) Thanks Max Vlasov _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
