On Sat, Sep 27, 2003 at 05:07:57PM -0500, Skip Montanaro wrote: > > Martin> Applications that don't want to suffer from the possible > Martin> serialization of CDB would need to use their own environment. > > I've given that a little more thought. Instead of encumbering the factory > functions which implement the old API with an optional dbenv argument, I > think if people want to provide their own environment it's reasonable to > expect them to use the new bsddb3 API. All we should do with the old API is > make it work in a multi-threaded environment if possible. > > Skip Agreed, that sounds like a good option. In my previous email I had forgotten about the DB_PRIVATE flag to DBEnv objects; that prevents them from writing extra DBEnv files to the filesystem for use when multi-process access is not needed. I just committed the small change needed to bsddb/__init__.py for it to use a DBEnv allowing multithreaded access. The original hammer.py from bug 775414 has been running for 15 minutes without problems on my alpha with BerkeleyDB 4.1.25. -g
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4