hyc@symas.com writes:

I guess that's a fair point, but operating without an entryCSN index would be a config mistake anyway. (Note that the unchecked limit only has relevance on backends that support indexing in the first place.)

As a user that's a config mistake from which I'd expect poor performance or sizelimit warnings in syslog, not broken CSN handling. In particular when slapo-syncprov(5) does mention indexing without demanding it:

"On databases that support inequality indexing, it is helpful to set an eq index on the entryCSN attribute when using this overlay."