RE: back-bdb quirk?

["Jonghyuk Choi" <jongchoi@us.ibm.com>]

Then, it may be a db4 problem.
As I replied to Pierangelo early this month,
increasing BDB_IDL_DB_SIZE seemed to solve
the cursor open-close mismatch problem
upon txn_prepare/txn_commit.
Anyway, it's great to have the new one...
- Jong

------------------------
Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
email: jongchoi@us.ibm.com
(phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979


"Howard Chu" <hyc@highlandsun.com> on 03/20/2002 05:08:24 PM

To:    Jonghyuk Choi/Watson/IBM@IBMUS, "Pierangelo Masarati"
       <masarati@aero.polimi.it>
cc:    <openldap-devel@OpenLDAP.org>
Subject:    RE: back-bdb quirk?



> -----Original Message-----
> From: Jonghyuk Choi [mailto:jongchoi@us.ibm.com]

> Pierangelo, increasing BDB_IDL_DB_SIZE worked in your case ?
>
> buf[BDB_IDL_DB_SIZE] of bdb_idl_insert_key can overflow while running
> bdb_idl_fetch_key().

Did you actually see this occur? I never did. At any rate, the new code
in HEAD doesn't have this risk.

> Although I'm also not 100% sure whether increasing
> BDB_IDL_DB_SIZE directly
> solves the problem,
> we seem to need a better management of IDL in memory.



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