#3446: Rate of `database is locked` errors is too high
------------------------------------+---------------------------------------
 Reporter:  cboos                   |        Owner:  jonas
     Type:  defect                  |       Status:  new  
 Priority:  normal                  |    Milestone:       
Component:  general                 |      Version:  devel
 Severity:  major                   |   Resolution:       
 Keywords:  database lock pysqlite  |  
------------------------------------+---------------------------------------
Comment (by cboos):

 Some random documents about SQLite and concurrent writes, for reference:
  - [http://www.somacon.com/p369.php Proposal for Improving Concurrency in
 SQLite]
  - [http://www.mikesclutter.com/sqlite/index.shtml Synchronized Locking in
 SQLite]
  - [http://www.sqlite.org/cvstrac/wiki?p=MultiThreading SQLite
 MultiThreading]
  - [http://www.sqlite.org/concurrency.html Improving Concurrency In
 SQLite], in particular section 4.0 ''Shorter transactions''
  - [http://www.sqlite.org/cvstrac/wiki?p=BlueSky the Shadow Pager idea],
 now that would be nice ;)

 Also, don't forget about
 [http://article.gmane.org/gmane.comp.db.sqlite.general/13002 locks
 triggered by concurrent writes], which we should now handle correctly
 (#2170 and #ps126).

-- 
Ticket URL: <http://trac.edgewall.org/ticket/3446#comment:2>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets

Reply via email to