Re[2]: (ITS#9136) mdb index degradation failure

[grapvar@gmail.com]

Howard Chu, 10 Dec 2019 19:30 MSK:
>
> Can you show that slapindex -t doesn't remove these index records?

I didn't know about. Yes, it removes the stale range records, thank you. And I have to backup database before, because of "quick mode", right?

However, periodical reindexing for index actualization is still required, but maintenance costs are lower.

Sorry for offtopic, but the messages from this mail list lose `References' and `In-Reply-To' smtp headers, is it intended? My MUA is unwilling to reconstruct mail threads, and the list archive web interface also teems with "<Possible follow-ups>".

grapvar@gmail.com, 10 Dec 2019 17:27 MSK:
>
> 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" records survive after slapindex
>   * they even survive after dropping/creating an index itself
>
> The only way to get rid of the "range" index records and actualize index is to create a new mdb and populate it from the ground up. This has maintainance costs.