"D. Richard Hipp" <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: > > 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). > > > > What you describe is not writer starvation. It is not clear to me how > what you describe is occurring.
Hmmm... Ok, well I'll have to investigate further. I had thought I was seeing a "known problem" and switching to 3.0 would solve the problem. Now I have a different sort of work to do, tracking this down. Thanks, Derrell
