Hello.
On Sat 2002-12-07 at 14:26:00 +0100, [EMAIL PROTECTED] wrote:
> Hello.
>
> On Fri 2002-12-06 at 16:13:54 -0600, [EMAIL PROTECTED] wrote:
> >
> > First off, we are using Innodb tables on version 3.23.53a-max.
> >
> > If the command STOP SLAVE is issued in the middle of the following type of
> > transaction:
> >
> > set autocommit = 0;
> > update...;
> > update...;
> > update...;
> > commit;
> >
> > does it roll back the current transaction or wait for it to complete?
[...]
> I decided to dig in the source a bit (v3.23.46).
[...]
> In short, it seems the slave thread effectively runs in auto-commit
> mode which is not what you want.
>
> I found a somewhat old post by Heikki (the InnoDB deveoper) which
> basically says the same:
>
> http://lists.mysql.com/cgi-ez/ezmlm-cgi?1:mss:79650
I just happened to see in the changelog, that this is out of date. As
of 3.23.52, it wraps BEGIN/COMMIT:
D.3.3 Changes in release 3.23.52 (14 Aug 2002)
* Wrap BEGIN/COMMIT around transaction in the binary log. This
makes replication honour transactions.
Sorry about that. Teaches me to not presume that there were no
important changes in the last few stable releases.
Bye,
Benjamin.
--
[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
