From: Christian Rabe
Date: November 1 2000 10:59am
Subject: Re: A suggestion on Replication
List-Archive: http://lists.mysql.com/internals/92
Message-Id: <043901c043f2$df2eb260$b401a8c0@gis.priv>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0434_01C043FB.3DE76100"

------=_NextPart_000_0434_01C043FB.3DE76100
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Yes, you are right.
User-variables are supported by replication neither.
So far I know (only what I read in the manual), user-variables are =
thread-bound. And therefore only the replication-thread on
the slave knows anything of them, if at all. So the values are lost on =
reconnect or the next flush slave at the latest.

Regards,

Christian "Maverick" Rabe
IT-Development
wallstreet:online AG
------------------------------------------
http://www.wallstreet-online.de
Tel.:  03 37 01 5 29 16
Fax.:  03 37 01 5 29 19
  ----- Original Message -----=20
  From: Wei He=20
  To: Christian Rabe=20
  Cc: internals@stripped=20
  Sent: Wednesday, November 01, 2000 3:18 AM
  Subject: Re: A suggestion on Replication


  On Thu, 26 Oct 2000, Christian Rabe wrote:

  Thanks for your instruction. I didn't have and change to try again =
until
  todayb I found my replication being interrupted again. In my
  environment, your first and third cases can be excluded.=20

  Instead of using temporary tables, I use variables like @ID, =
@tempid...
  Since the connection between my master and slave is poor, I wonder =
once=20
  the connection is broken, the @ID will lose its value when =
reconnected.
  I this case, hacking of slave.cc will not only of no help but =
dangerous.
  Am I right?=20

  Wei He





  > Hi,
  >=20
  > To 1: To accomplish this, you have to disable the lines 926-933 in =
the
  > sql/slave.cc (3.23.26)
  > To 2: This is already the case. Only successful master-querys are =
logged.
  > There are 3 cases, so far I know, when the
  >         slave gets a query to break on.
  >         First: there are Tables on the master that are not on the =
slave and
  > you write to them.
  >         Second: You use temporary tables,which are not temporary on =
the
  > slave and therefore not deletet afterward.
  >         So the Slave breaks the moment you try to recreate it on the =
master.
  >         In this two cases the command "SET SQL_LOG_BIN =3D 0" can =
help you,
  > which switches the logging off.
  >=20
  >         Third: You make a flush slave without a former flush master. =
The
  > slave reads
  >         then all existing logfiles anew which can lead to problems =
with
  > duplicate entries on the slave and BANG!
  >=20
  > I too had to use the dirty way of disabling the error with the =
drawback that
  > when there really is an error you won't notice it.
  >=20
  > Regards,
  >=20
  > Christian "Maverick" Rabe
  > IT-Development
  > wallstreet:online AG
  > ------------------------------------------
  > http://www.wallstreet-online.de
  > Tel.:  03 37 01 5 29 16
  > Fax.:  03 37 01 5 29 19
  >=20
  >=20
  > ----- Original Message -----
  > From: Wei He
  > To: internals@stripped
  > Sent: Thursday, October 26, 2000 4:45 AM
  > Subject: A suggestion on Replication
  >=20
  >=20
  > Hi,
  >=20
  > According to my experience, the replication will be broken when the =
slave
  > executes a error sql command. Can this be changed to:
  >=20
  > 1. The slave ignores the error and continues the replication;
  > 2. The master only bin-logs sql commands that succeed.
  >=20
  >=20
  > Wei He
  >=20
  >=20
  > =
---------------------------------------------------------------------
  > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" =
before
  > posting. To request this thread, e-mail =
internals-thread55@stripped
  >=20
  > To unsubscribe, send a message to the address shown in the
  > List-Unsubscribe header of this message. If you cannot see it,
  > e-mail internals-unsubscribe@stripped instead.
  >=20
  >=20
  > =
---------------------------------------------------------------------
  > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" =
before
  > posting. To request this thread, e-mail =
internals-thread56@stripped
  >=20
  > To unsubscribe, send a message to the address shown in the
  > List-Unsubscribe header of this message. If you cannot see it,
  > e-mail internals-unsubscribe@stripped instead.
  >=20
  >

------=_NextPart_000_0434_01C043FB.3DE76100--