I'm currently using lmdbjava 0.6.0 which uses LMDB 0.9.19 (retrieved via Meta.version()).

When using Linux setting a large map size is no problem: The database file grows with the size of the database. This is convenient as I can just use a very large value and I don't have to care about database resizing.

When using Windows (I'm using Windows 7) the database file size is always the same as the mapping size. E.g. when I set a map size of 100GB then the file size will be 100GB, too.

The LMDB inventor says this behavior has been changed (ITS#8324). The corresponding commit seems to be

fb5a768 Mon Nov 30 19:46:19 2015 ITS#8324 incremental DB file growth for Windows

which is from Nov. 30, 2016 and it should be included in LMDB 0.9.19.

However, the file size behavior under Windows still persists with lmdbjava 0.6.0. So I'm wondering:

• Did I misunderstand what ITS#8324 is supposed to do?
• Did lmdbjava bundle the wrong LMDB version?
• Or does the issue still exist in LMDB?

Any ideas?