Jeremiah Morrill wrote:
This sort of coincides with ITS issue 8347 I just reported.
With ldmb VL32, I’ve noticed that it can eat up a lot of memory space.
Sometimes ~500mb for an 800mb db after reading every record, one by one using
the same readonly transaction/cursor. I found that modifying M
This sort of coincides with ITS issue 8347 I just reported.
With ldmb VL32, I’ve noticed that it can eat up a lot of memory space.
Sometimes ~500mb for an 800mb db after reading every record, one by one using
the same readonly transaction/cursor. I found that modifying MDB_ERPAGE_SIZE
from 16
Le 2016-01-11 13:37, Michael Ströder a écrit :
M. P. wrote:
Further testing let me say that entries
that are present on the local server and not on the remote server,
will not be
displayed when searching the ldap server. When entries exists in both
servers,
the remote entries will be appended/
M. P. wrote:
> Further testing let me say that entries
> that are present on the local server and not on the remote server, will not be
> displayed when searching the ldap server. When entries exists in both servers,
> the remote entries will be appended/overwrited by local entries before being
> d
Le 2016-01-08 11:48, M. P. a écrit :
Hi,
We are on a process of merging datas from a remote database to a local
database. The two databases have the same base dn. To ease this
process, I thought for a way to make a union of the remote database
and the local database until remote datas are merged
