On 11/18/2015 03:37 PM, T?r?k Edwin wrote:
> On 11/17/2015 12:11 AM, Deon Brewis wrote:
>> We found that using SQLITE memory mapped I/O (mmap_size > 0) in OSX isn't
>> usable in any way shape or form. It will inevitably lead to catalog
>> corruption if you hard-reboot OSX, even without the
On 11/17/2015 12:11 AM, Deon Brewis wrote:
> We found that using SQLITE memory mapped I/O (mmap_size > 0) in OSX isn't
> usable in any way shape or form. It will inevitably lead to catalog
> corruption if you hard-reboot OSX, even without the database or application
> open.
>
I tried to turn
Dan Kennedy wrote:
> On 11/18/2015 03:37 PM, T?r?k Edwin wrote:
>> On 11/17/2015 12:11 AM, Deon Brewis wrote:
>>> We found that using SQLITE memory mapped I/O (mmap_size > 0) in OSX isn't
>>> usable in any way shape or form. It will inevitably lead to catalog
>>> corruption if you hard-reboot OSX,
On 11/18/15, Howard Chu wrote:
> Dan Kennedy wrote:
>>
>> As of yesterday, SQLite uses a read-only mapping in mmap mode. The db file
>> is
>> written using plain old write(), just as in non-mmap mode:
>
> That's the safest way to use mmap, but keep in mind that this requires a
> unified buffer
We found that using SQLITE memory mapped I/O (mmap_size > 0) in OSX isn't
usable in any way shape or form. It will inevitably lead to catalog corruption
if you hard-reboot OSX, even without the database or application open.
We've tried FULLSYNC and F_FULLFSYNC, but it makes no difference.
On 11/16/15, Deon Brewis wrote:
> We found that using SQLITE memory mapped I/O (mmap_size > 0) in OSX isn't
> usable in any way shape or form. It will inevitably lead to catalog
> corruption if you hard-reboot OSX, even without the database or application
> open.
>
> We've tried FULLSYNC and
6 matches
Mail list logo
