On Sat, Feb 22, 2014 at 12:48 PM, Holger Hans Peter Freyther holger@freyther.de wrote:
On Sat, Feb 22, 2014 at 12:19:09PM +0400, Alexey Shamrin wrote:
That said, it's not practical to never touch DB from outside and use only OpenBSC VTY interface. The latter doesn't allow custom SQL queries. Fortunately, the workaround is simple: issue `PRAGMA journal_mode = WAL` from `sqlite3` command once, when deploying OpenBSC.
To ask the other way around. Which queries do yo run? Do you UPDATE subscriber structures too?
SELECT only so far. We do not use UPDATE and INSERT or do this very rarely.
What I say is we need fixes and not work-arounds. The first step is making the code aware that a database lookup can take time.
I tend to agree that making WAL into the OpenBSC code doesn't worth the effort, which would be better spent on actually fixing the issue. It's easier to enable WAL from a script when we need to do so.