Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 451791 - parallel access to a database does not work
Summary: parallel access to a database does not work
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: sqlite
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 450664
Blocks: 449433
TreeView+ depends on / blocked
 
Reported: 2008-06-17 13:28 UTC by Stepan Kasal
Modified: 2008-06-17 14:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-17 14:45:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
test script (1017 bytes, text/plain)
2008-06-17 13:28 UTC, Stepan Kasal 		no flags Details
View All

Description Stepan Kasal 2008-06-17 13:28:33 UTC 
Two processes should be able to access the same database file simultaneously,
provided they commit timely.

3.5.8-1.fc10
The problem does not appear with 3.5.6-1.fc9 nor with 3.5.9.

See the attached reproducer.

With working sqlite, the output is:

$ ./t07busy8-lock
Ready

With a broken sqlite build, this is followed by two error messages:

DBD::SQLite::db do failed: database is locked(5) at dbdimp.c line 403 at ./t07bu
sy8-lock line 45, <READER> line 1.
Issuing rollback() for database handle being DESTROY'd without explicit
disconnect() at ./t07busy8-lock line 45, <READER> line 1.

According to my tests, this is fixed in sqlite-3.5.9, so if the suggestion from
bug #450664 is accepted, this should disappear.
Comment 1 Stepan Kasal 2008-06-17 13:28:33 UTC 
Created attachment 309615 [details]
test script
Comment 2 Stepan Kasal 2008-06-17 14:45:34 UTC 
sqlite has been updated, which should solve this issue as well
Note You need to log in before you can comment on or make changes to this bug.