On 12 Dec 2017, at 6:27pm, Jens Alfke <[email protected]> wrote:
> On Dec 12, 2017, at 5:46 AM, Simon Slavin <[email protected]> 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> Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
