Skip to content

libmdbx v0.13.12 "Аврора" (Aurora)

Latest

Choose a tag to compare

@erthink erthink released this 30 Apr 14:43
· 75 commits to master since this release
Immutable release. Only release title and notes can be modified.
v0.13.12
5315e99

The supporting release of a stable branch with bug fixes.

git diff' stat: 20 files changed, 191 insertions(+), 215 deletions(-)

Appreciations:

Important:

  • libmdbx project has changed its code development and distribution model.
    To get acquainted with important changes and plans, we recommend reading the compact presentation "libmdbx: successes, obstacles, goals and roadmap", which contains important explanations in the form of embedded comments.

  • At a many requests of users, the change log now is kept in English.

Fixes:

  • Fixed the counting of nested trees in the mdbx_chk tool for a multi-values/dupsort hives (backport).
  • Fixed swapping the shrink/growth parameters in a DB-geometry in the mdbx_load utility (backport).
  • Fixed SIGSEGV in the case when all meta pages are not entirely usable (backport).
  • Fixed information collection via kstat() for bootid on Solaris and related platforms (backport).
  • Fixed a typo in the ST_EXPORTED processing path that broke the build on platforms where the mentioned flag is defined for fstatvfs() (backport).
  • Fixed missing error handling of NtUnmapViewOfSection() and munmap() inside osal_munmap() (backport).
  • Fixed SIGSEGV due to an attempt to clean/overwrite a corrupted meta page when opening the database in read-only mode (backport).
  • Fixed returning a wrong/uninitialized ms_psize field when using mdbx_enumerate_tables() (backport).
  • Fixed adjusting of neighbor nested cursors after a dupsort item deletion (backport).

Other:

  • The dumps generated by the mdbx_dump utility no longer contains the current size of a DB and maxreaders parameter, so that the contents of a dump depend only on a payload data.
  • Cutoff packages/ into the separate aside repository.

Downloads:


For more information please see ChangeLog in the stable branch.