maria-developers team mailing list archive

[jocelyn fournier <jocelyn.fournier@xxxxxxxxx>]

Hi Jean,

Read uncommited is definitly treated differently on TokuDB (no snapshot 
read). You have a description of the kind of lock taken on TokuDB 
depending on the isolation level here :
https://github.com/Tokutek/tokudb-engine/wiki/Transactions-and-Concurrency

  Jocelyn




Le 25/11/2014 04:04, Jean Weisbuch a écrit :
> Transaction level only has effect on transactional engines (and note 
> that read uncommited is treated as read commited on TokuDB if i recall 
> correctly) thus the variable has no effect on MyISAM and Aria.
>
> Le 25/11/2014 03:48, Roberto Spadim a écrit :
> > hi guys, i use read uncommited sometimes with innodb, that's nice and 
> > work
> > but now, i'm using a myisam table, and a aria table....
> > does read uncommited work with this kind of engine? i tested and 
> > table stay 'waiting table lock' while a looooong update occurs
> > i don't know what's the internal diference but is possible to 
> > "easily" implement read uncommited to myisam/aria?
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-developers
> Post to     : maria-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp