On Fri, 13 Apr 2018, Howard Chu wrote:
I suppose so. Nobody says you have to use UFS for everything, just use
it for a data partition.
Yep, but I wanted the archives to show that using UFS, whilst solving the
problem with sparse files, could break other things on the Mac side, so
use it at
Howard:
So you are saying that on Android, Ios, and Windows 10, the
mdb_env_set_mapsize() will grow only as needed
and not pre-allocate the file space?
Only on MacOSX is there a funky behavior where I need to switch the
partition to UFS?
>From a commercial standpoint, that is not feasible. How
Dave Horsfall wrote:
On Thu, 12 Apr 2018, Howard Chu wrote:
[ Sparse files ]
If you want to get the behavior you're looking for, you need to switch to
UFS, which supports sparse files like most other POSIX filesystems.
But does that not also remove case-insensitivity,
Yes
leading to
On Thu, 12 Apr 2018, Howard Chu wrote:
[ Sparse files ]
If you want to get the behavior you're looking for, you need to switch
to UFS, which supports sparse files like most other POSIX filesystems.
But does that not also remove case-insensitivity, leading to failures in
Mac applications
mark diener wrote:
I came across a python write up about lmdb:
http://lmdb.readthedocs.io/en/release/#environment-class
map_size:
Maximum size database may grow to; used to size the memory mapping. If
database grows larger than map_size, an exception will be raised and
the user must close and
I came across a python write up about lmdb:
http://lmdb.readthedocs.io/en/release/#environment-class
map_size:
Maximum size database may grow to; used to size the memory mapping. If
database grows larger than map_size, an exception will be raised and
the user must close and reopen Environment.
