Receiving Database Locked Error Messages from Trac

Question

Surprisingly, someone got a known “database locked” error from Trac and how you solved it. This is starting to happen more and more for us. Will we really bite a bullet and move to another database, or is there another way?

For more information, see these two Trac error entries:

http://trac.edgewall.org/ticket/3446

http://trac.edgewall.org/ticket/3503

Edit 1 Thank you for the answer and recommendation, which seems to confirm our suspicion that switching to PostgreSQL seems to be the best option. The SQLite for the PostgreSQL script is here: http://trac-hacks.org/wiki/SqliteToPgScript Nothing is said here ...

Change 2 (solved) . The migration went pretty smoothly and I expect that we will no longer see the blockage. As far as I know, the speed is not noticeably better, but at least the locks have disappeared. Thank!

Answer 1

This is a problem with the current SQLite adapter. There are scripts for migrating to postgres, and I can really recommend that postgres are many accelerators for trac.

Answer 2

They just installed it on September 10th and the fix will be at 0.11.6.

http://trac.edgewall.org/ticket/3446#comment:39

Answer 3

, 100% . . 30 + , Trac, , . № 3446:

, [...] - ... concurrency