Hey Guys, Is there some way to check, using code, if a journal is hot? I'd like to be able to do this so I can automatically remove non-hot journals. Is there an SQLite api for opening/reading journals etc.? I've looked at the source and all the journal related stuff seems to be private.
I'm in a situation where my db is locking (write only) in some rare circumstances (I believe after some sort of crash while writing to the db, but I'm not sure). Others have told me it has also happened to them (on ext3 aswell as nfs). I was able to reproduce it once, but on an NFS partition. However I'm not entirely sure how, as far as I remember I ran a load of processes writing to the db, 50 or so on both cores, and killed them all with a killall command. Afterwards the db was write locked, and I had a journal file of size 512kb. However, I am able to read from it. Personally, I believe it may be an nfs lock, coping the sqlite db and db journal file to another location allows them to be written to. However, there is an initial read lock which becomes reset by writing to the db. I have not been able to reproduce the error since on nfs or ext3, the original db is still locked. Sometimes I also get a situation after a crash where the db is locked for both read and write, in this case I get a journal file with no permissions set of size 0kb. It happens on both nfs and ext3, removing the journal fixes the problem, modifying the permissions also fixes the problem. Thanks, Joe _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
