RE: commit: ldap/servers/slapd/back-bdb dbcache.c

["Howard Chu" <hyc@highlandsun.com>]

1) the patch hasn't been released. will it be in "the next release" ? don't
know.
2) one can always delete all the index files and run slapindex. whether
that's better
than slapcat/slapadd isn't clear, as slapindex is notoriously slow even
though it has
less work to do.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: Matthew Hardin [mailto:mhardin@symas.com]

> Will this require users to slapcat/slapadd to upgrade to the
> next release?
>
> -Matt
>
>
> > -----Original Message-----
> > From: owner-openldap-commit@OpenLDAP.org [mailto:owner-openldap-
> > commit@OpenLDAP.org] On Behalf Of hyc@OpenLDAP.org
> > Sent: Tuesday, January 27, 2004 8:01 PM
> > To: OpenLDAP Commit
> > Subject: commit: ldap/servers/slapd/back-bdb dbcache.c
> >
> > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb
> >
> > Modified Files:
> > 	dbcache.c  1.33 -> 1.34
> >
> > Log Message:
> > Use Btree instead of Hash for indexing
> >
> >
> > CVS Web URLs:
> >   http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/
> >     http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-
> > bdb/dbcache.c
> >
> > Changes are generally available on cvs.openldap.org (and CVSweb)
> > within 30 minutes of being committed.
>
>