Message27331
Problem confirmed on Python2.3.5/bsddb4.2.0.5 and
Python2.4.2/bsddb4.3.0 on Debian sid and Ubuntu Breezy.
It appears, that the associate call, necessary to
create a secondary index, segfaults when:
1. There is a large amount of data
2. Environment is transactional.
The
http://www.gramps-project.org/files/bsddb/testcase.tar.gz
contains the example code and two databases, pm.db and
pm_ok.db -- both have the same number of keys and each
data item is a pickled tuple with two elements. The
second index is created over the unpickled data[1]. The
pm.db segfaults and the pm_ok.db does not. The second
db has much smaller data items in data[0].
If the environment is set up and opened without TXN
then pm.db is also fine. Seems like a problem in
associate call in a TXN environment, that is only seen
with large enough data.
Please let me know if I can be of further assistance.
This is a show-stopper issue for me, I would go out of
my way to help resolving this or finding a work-around.
Thanks!
Alex
P.S. I could not attach the large file, probably due to
the size limit on the upload, hence a link to the testcase. |
|
Date |
User |
Action |
Args |
2007-08-23 14:37:25 | admin | link | issue1413192 messages |
2007-08-23 14:37:25 | admin | create | |
|