Berkeley DB page locking issue

[Database Administrator]

We faced following issue when we are using berkeley DB.
Problem: two cliient applications simultaneously accessing database;
one client is read mode and another is write mode. If we start read
operation in client1, client2 could not update the database is the
updation done in same page. It returns deadlock error in Db->put().

We checked the berkeley DB documentation and we using lock_detect()
for avoiding deadlock. can we disable internal page locking ?

we need to operate both read and write simultaneously in different
applications. There is any method for supporting our requirement ?

Thanks
Shanu

[Database Administrator]

On Feb 6, 10:27*am, shan...@gmail.com wrote:
> We faced following issue when we are using berkeley DB.
> Problem: two cliient applications simultaneously accessing database;
> one client is read mode and another is write mode. If we start read
> operation in client1, client2 could not update the database is the
> updation done in same page. It returns deadlock error in Db->put().
>
> We checked the berkeley DB documentation and we using lock_detect()
> for avoiding deadlock. can we disable internal page locking ?
>
> we need to operate both read and write simultaneously in different
> applications. There is any method for supporting our requirement ?
>
> Thanks
> Shanu

You can use the MVCC option in version 4.6.