Date: Tue, 05 Nov 2019 03:07:35 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 241385] databases/sqlite3: enable OS features Message-ID: <bug-241385-7788-mjDrRrZKTJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241385-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-241385-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241385 --- Comment #7 from rozhuk.im@gmail.com --- (In reply to Pavel Volkov from comment #6) SQLITE_MMAP_READWRITE - does not enables mmap() usage, it enables memcpy() = to mmaped memory write instead of lseek()+write() / pwrite(). I agree that it can be dangerous, or at least I do not know it there any bugs/features in FreeBSD mmap() implementations. But mmap() io does not enabled by this patch. To enable mmaped io some one should add -DSQLITE_DEFAULT_MMAP_SIZE=3D0x7fff= 0000 before compile this port, to force all apps use mmap() or execute "PRAGMA mmap_size=3D0x7fff0000" in app. I do not insist on SQLITE_MMAP_READWRITE, but if our mmap() implementation works as sqlite3 authors expect, then we get more profit from this. Yes, ~half of options is detected by autoconf, but I prefer to define it, j= ust to be sure that it set. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241385-7788-mjDrRrZKTJ>