List:Replication« Previous MessageNext Message »
From:ANIL YADAV Date:October 28 2011 3:01pm
Subject:Re: Temporary table issue (with replication)
View as plain text  
Hi David

I am using MySQL 5.1

On Fri, Oct 28, 2011 at 7:52 PM, David Lerer <DLerer@stripped>wrote:

> Anil, what MySQL version do you use?     David.
> -----Original Message-----
> From: David Lerer
> Sent: Friday, October 28, 2011 9:02 AM
> To: Replication
> Subject: RE: Temporary table issue (with replication)
> I was under the impression that this was considered a bug in earlier
> versions (pre 5.1) and it has been addressed.  It is really a serious
> replication problem if it still occurs.
> David.
> -----Original Message-----
> From: Johan De Meersman [mailto:vegivamp@stripped]
> Sent: Friday, October 28, 2011 7:49 AM
> Cc: Replication
> Subject: Re: Temporary table issue
> ----- Original Message -----
> > From: "ANIL YADAV" <uranil@stripped>
> > Is there no way to deal the situation ? As change is application Will
> > take a long time..
> I would assume that restarting your application would recreate the table on
> the master, and thus also on the slave.
> If that's not an option, but you're sure that there's only on connection
> from your application you could manually create the table on the slave, thus
> allowing replication to continue. That will not interfere with application
> startup, as a create temporary table statement naming an existing table will
> actually succeed and temporarily hide the permanent table of the same name;
> but you do need to make sure your application does not rely on the
> connection-specific nature of temporary tables, as all connections will see
> the same table, and that could cause wrong data to be used (two sessions
> writing private data into the same tabie...)
> --
> Bier met grenadyn
> Is als mosterd by den wyn
> Sy die't drinkt, is eene kwezel
> Hy die't drinkt, is ras een ezel
> The information contained in this e-mail and any attached
> documents may be privileged, confidential and protected from
> disclosure.  If you are not the intended recipient you may not
> read, copy, distribute or use this information.  If you have
> received this communication in error, please notify the sender
> immediately by replying to this message and then delete it
> from your system.

Thanks & Regards
"We judge ourselves by what we feel capable of doing,
while others judge us by what we have already done."

Re: Temporary table issue (with replication)ANIL YADAV28 Oct
  • Re: Temporary table issue (with replication)Johan De Meersman28 Oct