Re: Adding OU with PSQL backend

[Michael Ströder <michael@stroeder.com>]

Dieter Kluenter wrote:
> Marcel Berteler <marcel.berteler@bdsolutions.co.za> writes:
> 
>> Dieter Kluenter wrote the following on 2009/04/21 13:35:
>>> Marcel Berteler <marcel.berteler@bdsolutions.co.za> writes:
>>>
>>>> Should this directive work?
>>>>
>>>> index          regDate eq
>>>>
>>>> Where regDate is defined as follows:
>>>>
>>>> attributetype ( 1.3.6.1.4.1.22371.1.1 NAME 'regDate'
>>>>                DESC 'Registration Date'
>>>>                EQUALITY generalizedTimeMatch
>>>>                ORDERING generalizedTimeOrderingMatch
>>>>                SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
>>>>                SINGLE-VALUE )
>>>>
>>>> I can not seem to find a index type that specifically mentions time matches.
>>>>
>>> RFC-4517, section 3.3.13
>>>
>> Dieter, maybe its me, but that section does not clarify what indexing
>> directive I can use to speed up searching dates. It specifies the
>> format and content of Generalized Time.
> 
> Just a few lines down, section 4.2.16 and 4.2.17
> an equality index should be sufficient.

Server-side database indexing is implementation-specific and therefore
RFC 4517 does not say anything about indexing.

For indexing searches with <= or >= IMHO kind of an ordering index would
be needed for the ORDERING matching rule. Maybe one of the developers
could elaborate on how ordering matching works within slapd and whether
an equality index already speeds up this. When doing it with back-sql
probably the PostgresQL indexing configuration is relevant either.

Ciao, Michael.