Hello,
I'm wondering if shared cache and read uncommited isolation level with
asyncronous I/O enabled is possible ?
In sqlite3async.c I see a shared mutex between read and write operations, so
I doubt that it is possible to have real concurrency between read and
write...
Regards
--
View
Hello,
I'm wondering if shared cache and read uncommited isolation level with
asyncronous I/O enabled is possible ?
In sqlite3async.c I see a shared mutex between read and write operations, so
I doubt that it is possible to have real concurrency between read and
write...
Regards
--
View
Thanks,
I will try to use the shared cache with Async I/O
"Each shared-cache has its own mutex"...
So, does it possible to have more than one shared cache within a single
process ?
One shared cache by db ?
--
View this message in context:
To be more precise I would like to parallelize writes operations on different
tables, so potentially in different db (files).
It's why I think about using multi databases (1 by table), the shared cache
system and the asynchronized I/O..
So if a shared cache is shared accross different
I'm confused according to Dan Kennedy :
"Each shared-cache has its own mutex. The mutex is held for the duration
of each sqlite3_step() call. So the way you're defining it here, you
can't have "real" concurrency when using shared-cache mode in any case. "
So, it's a little bit "antagonist" to
time spent in sqlite3_step() will be spent in a single call
to sqlite3VdbeExec(), so the effect is similar.
Dan.
> Pavel
>
> On Wed, Nov 18, 2009 at 8:40 AM, presta <harc...@gmail.com> wrote:
>>
>> I'm confused according to Dan Kennedy :
>>
>> "E
Hi,
With shared cache enabled, if we want to attach a database to the current
connection does sqlite create a new shared cache for the new attached
database or does it share the same shared cache ?
Thanks
--
View this message in context:
In fact I want to work on 2 different database.
1 connection (cx1) with the db1 for write operations (shared cache enabled,
read uncommited)
1 connection (cx2) with the db2 for write operations (shared cache enabled,
read uncommited)
And another connection (or cx1) with both db1 and db2
>No, it's one write transaction per table.
Wierd, according to the doc : "At most one connection to a single shared
cache may open a write transaction at any one time. This may co-exist with
any number of read transactions"
--
View this message in context:
9 matches
Mail list logo