[EMAIL PROTECTED] wrote:
I'll look into adding a PRAGMA that makes BEGIN TRANSACTION acquire
a RESERVED lock immediately. That will reduce the amount of confusion
about this issue, I suppose.
Does enabling this PRAGMA regenerate the reader starvation problem of 2.8.x,
or is that problem solved elsewise in 3.0?
Version 2 had a problem with writer starvation. I'm not familiar with
the reader starvation problem. Can you describe your situation?
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.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
