Hi there,
My apologies if this has been answered in the past, but is there a reason
for the ~2GB default for SQLITE_MAX_MMAP_SIZE ?
#ifndef SQLITE_MAX_MMAP_SIZE
...
# define SQLITE_MAX_MMAP_SIZE 0x7fff0000 /* 2147418112 */
It makes sense for 32bit platforms, but for 64bit with larger databases
(where 2GB ends up being a small fraction of the db file), the default max
effectively takes away the benefit of the feature.
I can compile my own binary of course, but it would be convenient to have
it supported out of the box.
Just wondering if there is a reason not to increase the max for 64bit
builds (to some large value like 1TB) ? Especially given that that the
default mmap size is much lower in any case until it is increased (with
PRAGMA mmap_size).
Thanks..!
Carl
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
