[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: How indexes used with search

To: openldap-technical@openldap.org
Subject: Re: How indexes used with search
From: Roman Rybalko <openldap@romanr.name>
Date: Wed, 26 Sep 2012 15:35:36 +0400
In-reply-to: <50618E15.2000105@romanr.name>
References: <50616836.7070305@romanr.name> <50618985.8080100@symas.com> <50618E15.2000105@romanr.name>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0

25.09.2012 14:57, Roman Rybalko ÐÐÑÐÑ:
> Also it's not clear for me how objectID set is determined when there
> is search on "one" scope? The same when "sub" scope cover not the full
> database contents but a part of the object tree (suffix: cn=test,
> search base: cn=test1,cn=test)? I thought that search with base
> covering not the full backend suffix (but a partial tree) should work
> faster, but seems this is not true, even overhead introduced by
> additional objectID set. Right? 
Howard, can you explain it please?

-- 
WBR,
Roman Rybalko

Follow-Ups:
- Re: How indexes used with search
  - From: Howard Chu <hyc@symas.com>

References:
- How indexes used with search
  - From: Roman Rybalko <openldap@romanr.name>
- Re: How indexes used with search
  - From: Howard Chu <hyc@symas.com>
- Re: How indexes used with search
  - From: Roman Rybalko <openldap@romanr.name>

Prev by Date: Re: ldapsearch stalling when performing searches with a large number of results
Next by Date: Ldap search that must work
Index(es):
- Chronological
- Thread