> Le 9 juil. 2016 à 00:55, Brian Vincent <[email protected]> a écrit : > > I've managed to reproduce a scenario where one database, database1.db is > rebuilding a large wal-index. Meanwhile, all other threads attempting to > open completely unrelated databases (e.g. database2.db) are blocked until > the wal-index on database1.db is finished rebuilding. This is obviously > undesirable.
It probably is. *I* can't comment or recommend anything on what you described but I'm really interested in knowing wether you use the engine in SERIALIZED or MULTITHREADED mode during this event reproduction? And assuming it is the default mode SERIALIZED which is used, wether it is different when run in MULTITHREADED mode (in which the engine code is supposed to do much less contention between threads, in exchange for the app responsibility not to share any connection (and dependent structures like statements) between threads. -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
