Is there any turnround to be done while using 5.0.32?
Would the use of
transaction_isolation=SERIALIZABLE help ?
Thanks in advance for your help ?
Mariella
--- Sunny Bains <Sunny.Bains@stripped> wrote:
> Mariella,
>
>
> Mariella Petrini wrote:
> > Hi,
> >
> >
> > I have been using 5.0.32 MySQL on Debian.
> > Everything worked properly.
> > DRBD has been added and configure with MySQL and
> > restarted.
> > The tables used are InnoDB type and use
> > auto_increment.
> >
> > After that during INSERTs and UPDATEs innodb
> started
> > to roll back
> > for table lock on AUTO_INC
>
> The behavior observed is most likely related to this
> bug report:
>
> http://bugs.mysql.com/bug.php?id=16979
>
> Regards,
> -sunny
>
> Oracle/Innobase.
>
____________________________________________________________________________________
Yahoo! oneSearch: Finally, mobile search
that gives answers, not web links.
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
