grap...@gmail.com wrote:
> Contrast to bdb, the "range" index records are immortal in the mdb:
>
> * they offer many-thousand list of search candidates (in terms of
> mdb_search())
> for particular attribute value even if all instances of this value are removed
> from the dit.
> * "range"
Howard Chu, 02 Dec 2019 18:20 MSK:
>
> Since this is allocated in thread-local memory, there is no actual leak.
If so, why does the op->o_tmpfree() exist ?
Konstantin Andreev.
Konstantin Andreev, 02 Dec 2019 16:57 MSK:
>
> mdb_entry_decode() leaks allocated [Entry] on error. Here is a fix for
Full_Name: Konstantin Andreev
Version: 2.4.48, git/master/44a7b46/20191203
OS: Solaris 11.3 x64
URL:
Submission from: (NULL) (79.135.238.172)
When
* the number of entries containing particular attr/val, e.g. `o=1', reaches
MDB_IDL_DB_MAX+1 ( = 0x1 = 65536 ), and
* this attribute is
Full_Name: Konstantin Andreev
Version: 2.4.48, git/master/44a7b46/20191203
OS: Solaris 11.3 x64
URL:
Submission from: (NULL) (79.135.238.172)
Here is a test case.
1) choose an attribute that has an equality index in your dit;
2) for this attribute choose a value that does not (and did
