[pybsddb] Problem scanning large hashed database

[andrew]

I seem to have it sorted now. The problem was that my scanning code was
specifying the following locks when opening the database:

db.DB_CREATE|db.DB_INIT_MPOOL|db.DB_INIT_LOG|db.DB_INIT_TXN|
db.DB_INIT_LOCK|db.DB_RECOVER

After actually reading the documentation, I stripped it right back to
just:

db.DB_INIT_MPOOL

and all seemed to work fine.

Cheers, Andrew.

On Thu, 2008-12-04 at 08:54 -0500, Will Weisser wrote:
> I get the same error in my original process when starting another
> process which calls lock_detect on the same database.  I suspect a
> problem with the python binding as the db_deadlock utility does not
> show the same behavior.
> 
> On Wed, Dec 3, 2008 at 8:58 PM, andrew <andrew at reurbanise.co.nz>
> wrote:
>         Hi All,
>         
>         I have a large-ish production database (1.6M objects) that
>         usually gets
>         accessed only for reads on writes on specific keys, for which
>         it is nice
>         and fast. However, I need to be able to do some adhoc queries
>         on this
>         data occasionally and I seem to be running into some problems
>         doing
>         that.

>