[sqlite] valgrind report (uninitialized byte) while committing large transaction

Hi, I am seeing the valgrind error below using sqlite 3.6.18. It seems to always happens while committing a transaction having 100 INSERT(s). all INSERT are done in one single table. Is this a known issue? Thanks Vincent ==15065== ==15065== Thread 71: ==15065== Syscall param write(buf)

Re: [sqlite] Multiple connection to in-memory database

tmpfs looks like the best approach for us since we then can use concurrent transactions using multiple connections from different threads and with good performances. I didn't know /tmp was mounted as a tmpfs. Thanks all for the replies. Vincent Brandon, Nicholas (UK) wrote: >> I would like t

[sqlite] Multiple connection to in-memory database

Hi, I would like to use transactions from separate threads, each thread having one connection to a single in-memory db. I just read in the sqlite doc that in-memory sqlite databases (using sqlite3_open(":memory:", ...)) are private to a single connection. Is there a way to open a second connect