Berkeley DB page locking issue

#1

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

#2

On Feb 6, 10:27*am, shan... (AT) gmail (DOT) com wrote:

Quote:

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.

#3

On Feb 6, 10:27*am, shan... (AT) gmail (DOT) com wrote:

Quote:

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.

#4

On Feb 6, 10:27*am, shan... (AT) gmail (DOT) com wrote:

Quote:

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.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Berkeley DB page locking issue

comp.databases.berkeley-db comp.databases.berkeley-db

Berkeley DB page locking issue - 02-06-2008 , 09:27 AM

Re: Berkeley DB page locking issue - 03-12-2008 , 01:02 PM

Re: Berkeley DB page locking issue - 03-12-2008 , 01:02 PM

Re: Berkeley DB page locking issue - 03-12-2008 , 01:02 PM