Re: [sqlite] Reason for random names for the master journal?

2011-02-25 Thread Dan Kennedy
>> For example, say you have two databases in a transaction - mine.db >> and yours.db. A crash happens while committing the transaction >> and the file mine.db-mjMASTER is left in the file-system. >> >> Following recovery, if a process tries to read mine.db, the >> transaction on mine.db will be

Re: [sqlite] Reason for random names for the master journal?

2011-02-25 Thread Drake Wilson
Quoth Johns Daniel , on 2011-02-25 16:21:54 -0600: > Thank you very much for this info, Dan! Very useful. > > >From your description, it sounds like this requirement only applies if > there are 3 or more databases. Is this an issue with 2 databases? Yes, master journals

Re: [sqlite] Reason for random names for the master journal?

2011-02-25 Thread Johns Daniel
On Fri, Feb 25, 2011 at 12:04 PM, Dan Kennedy wrote: > On 02/26/2011 12:30 AM, Johns Daniel wrote: >> What is the reason was for having random filenames for the SQLite >> master journal file (like mine.db-mj501CA440, mine.db-mj1C17, >> mine.db-mj66677495, etc)? >> >>

Re: [sqlite] Reason for random names for the master journal?

2011-02-25 Thread Dan Kennedy
On 02/26/2011 12:30 AM, Johns Daniel wrote: > What is the reason was for having random filenames for the SQLite > master journal file (like mine.db-mj501CA440, mine.db-mj1C17, > mine.db-mj66677495, etc)? > > Here is the reason for this strange question. We have discovered that > the JFFS2

[sqlite] Reason for random names for the master journal?

2011-02-25 Thread Johns Daniel
What is the reason was for having random filenames for the SQLite master journal file (like mine.db-mj501CA440, mine.db-mj1C17, mine.db-mj66677495, etc)? Here is the reason for this strange question. We have discovered that the JFFS2 filesystem in Linux is leaking kernel memory each time we