Quanah Gibson-Mount wrote: > --On Tuesday, September 1, 2020 11:18 AM +0000 chrichardso27(a)gmail.com > wrote: > > > > > "(&(objectClass=someClass)(abc=cn=foo,dc=bar,cn=server,ou=system,cn=direc > > tory,dc=example,dc=org))" > > foo and bar are the actual real values? dc=example,dc=org is your domain?
The depth is the same, the values are different from the actual that we use. I cannot share the actual values without disclosing internal details. > > > > > > > b) The schema definition of the attribute in question. > > > > attributetype ( > > 1.3.6.1.4.1.14761.1.26 > > NAME 'abc' > > DESC 'A description' > > EQUALITY distinguishedNameMatch > > SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' ) > > abc is your actual attribute name? Same as above, I cannot disclose the actual values but to give it a bit more meaning, lets say that the attribute name could be for example "userSystemDN". > > And don't waste time with back-bdb, it's deprecated and removed from 2.5+. This is known. However, this happens to be a critical issue at the moment with BDB. Futhermore, I can reproduce the problem with MDB but the search filter execution time drops to around 2 seconds. Still, in a high volume system, this is not acceptable. Other values in this same attribute perform in tens of milliseconds. The one specific value (which I cannot disclose here) is extremely slow compared to similar data, just with different DN value. > > Regards, > Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com>
