On 12.12.2017 19:47 Simon Slavin wrote: > On 12 Dec 2017, at 6:27pm, Jens Alfke <j...@mooseyard.com> wrote: > >> On Dec 12, 2017, at 5:46 AM, Simon Slavin <slav...@bigfraud.org> wrote: >>> Before you answer that question, you should know that both Windows and >>> macOS have been proved to have serious bugs in their memory mapping code. >> This has been brought up several times recently, but I’ve never seen any >> details given about exactly what was wrong with macOS’s mmap implementation. >> Does anyone have a pointer to authoritative information about this? > See this thread: > > <http://sqlite.1065341.n5.nabble.com/SQLITE-vs-OSX-mmap-inevitable-catalog-corruption-td85620.html> > > This is the thread which led to memory mapping being disabled for writing on > macOS, as discussed here: > > <http://sqlite.1065341.n5.nabble.com/Re-Database-corruption-and-PRAGMA-fullfsync-on-macOS-td95366i20.html>
There might also be a mmap bug in the Android 7.0 fuse layer: https://www.mail-archive.com/openldap-its@openldap.org/msg10970.html _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
