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 of certain environment variables.
The answer is often "yes" but depending on the conditions above
it can sometimes be "no". Your safest bet is to assume "no".
Is there any way to get more information on the deadlock or how to avoid it?
The best advice I know of is to not use threads. Use
full-blown processes instead. But I'm guessing you will
not be heeding that advice, so apart from that, no I
don't have any other suggestions. Sorry.
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.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
