On 7/31/18, Andrzej Fiedukowicz <afiedukow...@gog.com> wrote: > * The issue was pinpointed to be caused by timeout on > `sqlite3_open_v2` which supposedly takes over 60s to complete (we only > give it 60s).
Are you sure the time is happening on sqlite3_open_v2()? Because that routine just opens the file descriptors but never reads from the database files. Perhaps Poco is doing something else (like setting some PRAGMAs or something) after the sqlite3_open_v2() call? Anyhow - if the database needs recovery, the first thing that SQLite will do will run recovery. And if the database is large and the transaction(s) that are being recovered are large, and if your machine is slow, then I suppose that could take a long time. Even so, 60 milliseconds seems like a more reasonable number than 60 seconds. I don't know what is going on. I wish you could reproduce the problem. AV software is also notorious for causing problems on Windows machines. That might also be a problem. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
