Skip to content
This repository has been archived by the owner on Sep 13, 2023. It is now read-only.

Fix support for larger than 2 GB databases on Windows #24

Closed
wants to merge 6 commits into from
Closed

Fix support for larger than 2 GB databases on Windows #24

wants to merge 6 commits into from

Commits on Dec 30, 2018

  1. Add test to verify that the file is allocated sparsly. 

    This will fail on older versions of LMDB on Windows
that doesn't have the ITS#3824 fix
    @repi
    repi committed Dec 30, 2018
    Configuration menu
    Copy the full SHA
    d51b3c8 View commit details
    Browse the repository at this point in the history

  2. Update to latest master version of LMDB (2018-09-19). 

    This includes important improvements such as ITS#8324
which enables sparse file allocation on Windows
    @repi
    repi committed Dec 30, 2018
    Configuration menu
    Copy the full SHA
    bca6f3e View commit details
    Browse the repository at this point in the history

  3. Switch to use our lmdb-sys from this repo instead of creates.io version

    @repi
    repi committed Dec 30, 2018
    Configuration menu
    Copy the full SHA
    c5abf05 View commit details
    Browse the repository at this point in the history

Commits on Dec 31, 2018

  1. Add test to verify that one can create DB larger than 2 GB.

    @repi
    repi committed Dec 31, 2018
    Configuration menu
    Copy the full SHA
    738bc40 View commit details
    Browse the repository at this point in the history

  2. Fix support for larger than 2 GB databases on Windows. 

    This was discussed and allegedly fixed in LMDB in January 2016 by defining
_FILE_OFFSET_BITS but that doesn't work because Windows headers do not
support that POSIX define.

In this fix I re-define `off_t` in build.rs to int64 instead.

Original discussion and non-working fix:

https://www.openldap.org/lists/openldap-bugs/201605/msg00015.htm

LMDB/lmdb@20dec1f

Should be fixed properly in upstream LMDB though, this is a workaround until then.
    @repi
    repi committed Dec 31, 2018
    Configuration menu
    Copy the full SHA
    5ad7962 View commit details
    Browse the repository at this point in the history

Commits on Jan 18, 2019

  1. Upgrade lmdb to latest from mdb.master

    @repi
    repi committed Jan 18, 2019
    Configuration menu
    Copy the full SHA
    0d9c604 View commit details
    Browse the repository at this point in the history