Re: [sqlite] SQLite 3.08 Deadlock in a Linux Multithreaded Multi-Process Application

2004-12-21 Thread Corwin Burgess
D. Richard Hipp wrote: For additional information on the brokenness of POSIX advisory locks and of POSIX threads, and in particular how they are especially broken when used together, read the comments in the source file os_unix.c. After reading D. Richard Hipp's reply to this message I did a

Re: [sqlite] SQLite 3.08 Deadlock in a Linux Multithreaded Multi-Process Application

2004-12-02 Thread Andrew Piskorski
On Thu, Dec 02, 2004 at 11:33:33PM +0200, Ron Avriel wrote: > Hi, > I'm using SQLite 3.0.8 on Linux in an Apache module, in a > multithreaded multi-process configuration. Occasionally, the database BOTH mulit-threaded and multi-process? Why are you doing that? Is this some sort of special

Re: [sqlite] SQLite 3.08 Deadlock in a Linux Multithreaded Multi-Process Application

2004-12-02 Thread D. Richard Hipp
Ron Avriel wrote: Is it OK to use the same sqlite3 session in multiple threads but making sure that at anytime it is used by only one thread? That depends on a number of things, including (but not limited to) your Linux kernel version, the particular threading library you are using, and the state

[sqlite] SQLite 3.08 Deadlock in a Linux Multithreaded Multi-Process Application

2004-12-02 Thread Ron Avriel
Hi, I'm using SQLite 3.0.8 on Linux in an Apache module, in a multithreaded multi-process configuration. Occasionally, the database becomes deadlocked - all requests fail with a busy error. Even when I try to access it using sqlite command line I get "Error: database is locked" for every