From 061750bccb90e12604e62e12c62baf434a342914 Mon Sep 17 00:00:00 2001 From: Leonid Yuriev Date: Mon, 24 Aug 2020 01:01:44 +0300 Subject: [PATCH] mdbx-doc: fix LMDB/MDBX typo. Change-Id: I6e492eebc43cde7ef274e9f64559f401500a780b --- docs/_restrictions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_restrictions.md b/docs/_restrictions.md index 03c76cb9..4f44e886 100644 --- a/docs/_restrictions.md +++ b/docs/_restrictions.md @@ -144,7 +144,7 @@ reasonable to simplify this as follows: A good example of long readers is a hot backup to the slow destination or debugging of a client application while retaining an active read -transaction. LMDB this results in `MDBX_MAP_FULL` error and subsequent write +transaction. LMDB this results in `MDB_MAP_FULL` error and subsequent write performance degradation. MDBX mostly solve "long-lived" readers issue by the lack-of-space callback