On Apr 09, Zardosht Kasheff wrote:
> Hello Sergei,
> Is there a patch available for this? Also, was this the only issue to
> fix in order to get MariaDB working with multiple XA supporting
> storage engines?
No, I just fixed it in MariaDB. But, of course, you can extract the
patch with bzr.
There were two issues. After I fixed the first one - a crash - a second
one started showing up. Incorrect mutex locking order (that can cause
deadlocks). It was found by MariaDB built-in mutex deadlock detector,
in MySQL it would've slipped in unnoticed.
This bug is fixed too, of course.
> On Mon, Apr 9, 2012 at 12:01 PM, Sergei Golubchik <serg@stripped> wrote:
> > Hi, Zardosht!
> > On Apr 09, Zardosht Kasheff wrote:
> >> I am trying to add XA for our storage engine in 5.1.61, and am running
> >> into http://bugs.mysql.com/bug.php?id=47134.
> >> Does anyone have experience with adding a storage engine (in addition
> >> to InnoDB) that supports XA to MySQL? Does 5.5 have this problem?
> >> MariaDB?
> > No. It was fixed in MariaDB 5.1 almost two years ago.
> > Regards,
> > Sergei
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: http://lists.mysql.com/internals