获取“数据库已锁定” 来自 Trac 的错误消息
想知道是否有人收到 Trac 臭名昭著的“数据库已锁定”错误以及您是如何解决的。 它开始越来越频繁地发生在我们身上。 我们真的必须硬着头皮迁移到不同的数据库后端，还是有其他方法？
有关详细信息，请参阅这两个 Trac 错误条目：
http://trac.edgewall.org/ticket/3446< /a>
http://trac.edgewall.org/ticket/3503
编辑1 感谢您的回答和建议，这似乎证实了我们的怀疑：迁移到 PostgreSQL 似乎是最好的选择。 SQLite 到 PostgreSQL 脚本位于：http://trac-hacks.org/wiki/SqliteToPgScript 这里没有任何内容...
编辑 2（已解决） 迁移进行得非常顺利，我希望我们不会再看到锁。 据我所知，速度并没有明显提高，但至少锁消失了。 谢谢！
Wondering if anyone has gotten the infamous "database is locked" error from Trac and how you solved it. It is starting to occur more and more often for us. Will we really have to bite the bullet and migrate to a different DB backend, or is there another way?
See these two Trac bug entries for more info:
http://trac.edgewall.org/ticket/3446
http://trac.edgewall.org/ticket/3503
Edit 1 Thanks for the answer and the recommendation, which seems to confirm our suspicion that migrating to PostgreSQL seems to be the best option. The SQLite to PostgreSQL script is here: http://trac-hacks.org/wiki/SqliteToPgScript Here goes nothing...
Edit 2 (solved) The migration went pretty smooth and I expect we won't be seeing the locks any more. The speed isn't noticeably better as far as I can tell, but at least the locks are gone. Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这是当前 SQLite 适配器的问题。 有一些脚本可以迁移到 postgres，我真的可以推荐，postgres 对于 trac 来说速度要快很多。
That's a problem with the current SQLite adapter. There are scripts to migrate to postgres and I can really recommend that, postgres is a lot speeder for trac.
他们刚刚在 9 月 10 日修复了这个问题，修复将在 0.11.6 中进行。
http://trac.edgewall.org/ticket/3446#comment:39
They just fixed this on Sept 10, and the fix will be in 0.11.6.
http://trac.edgewall.org/ticket/3446#comment:39
我认为这还没有 100% 解决。 我们每天都会遇到这个错误几十次。 在我们的例子中，我们有 30 多人不断更新 Trac，因为我们使用它来跟踪几乎所有内容，而不仅仅是错误。 来自票#3446：
I don't think this is 100% fixed just yet. We experience this error a couple dozen times a day. In our case, we have 30+ people updating Trac constantly as we use it for tracking pretty much everything, and not just bugs. From ticket #3446: