"D. Richard Hipp" <[EMAIL PROTECTED]> writes: > Version 2 had a problem with writer starvation. I'm not familiar with > the reader starvation problem. Can you describe your situation?
Maybe I misremembered the terminology. What I'm seeing is a few tasks doing lots of writing to the database (with and without explicit transactions) preventing a reader task from getting a chance to read. A SELECT can block for a *very* long time (my 60 second timeout expires). > The PRAGMA would still using the PENDING lock idea so I think the > writer starvation problem would still be resolved. The PRAGMA would > just disallow multi-statement read-only transactions. Ok, great. Now is what I just described above what you had called "writer starvation"? Cheers, Derrell
