That said, whenever you write an entry you always have seen the parent and could stack the dn with the parentid and createt the dn without using the entryrdn index.
You even need not to keep track of all the entry rdsn/dns - only the ones with children will be needed later, the presence of "numsubordinates"
identifies a parent.

Interesting. I think I now understand better how to approach this problem.

I'll get back to it soon.

Thanks so much!

> Last but not least, since I think dbscan is broken for entryrdn, investigating and fixing this would also be nice

Sure. I'll open a ticket so it gets tracked.