Non-indexed searches on objectclass?

objectclass is indexed by default, so you shouldn't have to
add it.

Maybe your searches are exceeding the All IDs threshold.
Take a look at:
http://www.redhat.com/docs/manuals/dir-s
erver/ag/7.1/index1.html#1110655

Philip Kime wrote:
> When I look at the logconv output for some of my FDS
servers, I see 
> that the common factor on all listed unindexed searches
is using the 
> "objectclass" attribute. Is it worth indexing
this?
>  
> PK
>  
> --
> Philip Kime
> NOPS Systems Architect
> 310 401 0407
>  
>
------------------------------------------------------------
------------


--
Fedora-directory-users mailing list
Fedora-directory-usersredhat.com
https://www.redhat.com/mailman/listinfo/fedora-dir
ectory-users

Philip Kime wrote:
> When I look at the logconv output for some of my FDS
servers, I see 
> that the common factor on all listed unindexed searches
is using the 
> "objectclass" attribute. Is it worth indexing
this?
>
It is already indexed for equality. The fact that an
attribute is 
indexed does not mean all searches using it will be indexed
searches. In 
an attempt to perform _less_ work, when the number of
candidate entries 
returned by an index exceeds administrative limits it
triggers an 
unindexed search. Also the type of index must match the
search filter 
type. As db of size increases, objectclass becomes less and
less likely 
to actually distinguish entries sufficiently to be useful,
and certainly 
not with any index type other than equality.

-- 
Pete


--
Fedora-directory-users mailing list
Fedora-directory-usersredhat.com
https://www.redhat.com/mailman/listinfo/fedora-dir
ectory-users