DDL for temporary tables is replicated
Bug #903217 reported by
Seppo Jaakola
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
Low
|
Seppo Jaakola | ||
5.1 |
Won't Fix
|
Low
|
Seppo Jaakola | ||
5.5 |
Fix Released
|
Low
|
Seppo Jaakola |
Bug Description
DDL statements related to temporary tables seems to be replicated. This is unnecessary and should be avoided.
Howto reproduce:
1. start two nodes and enable wsrep debugging.
2. issue in node1:
CREATE TEMPORARY TABLE test.t (i int);
DROP TABLE test.t;
3. browse error log in node2
To post a comment you must log in.
I follow the bug#
DDL statements related to temporary tables seems to be replicated.
This is unnecessary and should be avoided.
Howto reproduce:
1. start two nodes and enable wsrep debugging.
2. issue in node1:
CREATE TEMPORARY TABLE test.t (i int);
DROP TABLE test.t;
3. browse error log in node2
When i run this
CREATE TEMPORARY TABLE test.t (i int);
DROP TABLE test.t;
------> I didn't receive any error.... but when i run on my database
which with name ets... on Node 1
i run this query ..... [SQL] create temporary table contractSigned as Sign_Date, A.BP_Id, C.CD_Id, Of_Training, C.Length_ Of_Employment, Percentage, C.After_ Training_ Percentage, ADD(D.AIS_ Date,interval C.Length_ Of_Training month) ) as D.AIS_Date, interval (C.Length_ Of_Training Of_Employment) month) ) as EmploymentEnd from cbp_bpprofile A, iverable C, cbp_cdiplan D where A.BP_Id Sign_Date != '0000-00-00' and D.PNSFD_Month != 0 and Contract_ Sign_Date) >= '2008'
select B.Contract_ID, B.Contract_
B.Start_Date, C.Length_
C.Training_Fee, C.Training_
C.TotalSlot, D.AIS_Date, D.PNSFD_Month,
Date(DATE_
trainingEnd, Date( DATE_ADD(
+Length_
cbp_contract B, cbp_contractdel
= B.BP_Id and B.Contract_ID = C.Contract_ID and C.CD_Id = D.CD_Id and
B.Contract_
A.Industry_Type != '' and A.Industry_Type = 359 and
Year(B.
[Err] 2003 - Can't connect to MySQL server on '10.10.5.105' (10061)
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -------
Logs from Node 2::::
111212 21:06:26 [Note] WSREP: (701dfd2a- 24c5-11e1- 0800-8daf717742 92, 0.0.0.0: 4567') turning message relay requesting on, nonlive 10.5.105: 4567 24c5-11e1- 0800-8daf717742 92, 0.0.0.0: 4567') reconnecting to 24c5-11e1- 0800-930e8a02f5 ed (tcp:// 10.10.5. 105:4567) , attempt 701dfd2a- 24c5-11e1- 0800-8daf717742 92, OPERATIONAL, REG,34da9138- 24c5-11e1- 0800-930e8a02f5 ed,2)) suspecting node: 24c5-11e1- 0800-930e8a02f5 ed 10.5.105: 4567 24c5-11e1- 0800-930e8a02f5 ed -> 24eb-11e1- 0800-8b54d5fdd8 57 24c5-11e1- 0800-8daf717742 92, 0.0.0.0: 4567') turning message relay requesting off 701dfd2a- 24c5-11e1- 0800-8daf717742 92, GATHER, view_id(REG, 24c5-11e1- 0800-930e8a02f5 ed,2)) suspecting node: 24c5-11e1- 0800-930e8a02f5 ed 701dfd2a- 24c5-11e1- 0800-8daf717742 92, GATHER, view_id(REG, 24c5-11e1- 0800-930e8a02f5 ed,2)) suspecting node: 24c5-11e1- 0800-930e8a02f5 ed 701dfd2a- 24c5-11e1- 0800-8daf717742 92, GATHER, view_id(REG, 24c5-11e1- 0800-930e8a02f5 ed,2)) suspecting node: 24c5-11e1- 0800-930e8a02f5 ed 701dfd2a- 24c5-11e1- 0800-8daf717742 92, GATHER, view_id(REG, 24c5-11e1- 0800-930e8a02f5 ed,2)) suspecting node: 24c5-11e1- 0800-930e8a02f5 ed 701dfd2a- 24c5-11e1- 0800-8d. ..
'tcp://
peers: tcp://10.
111212 21:06:27 [Note] WSREP: (701dfd2a-
'tcp://
34da9138-
0
111212 21:06:30 [Note] WSREP:
evs::proto(
view_id(
34da9138-
111212 21:06:30 [Note] WSREP: remote endpoint tcp://10.
changed identity 34da9138-
d1a5601c-
111212 21:06:30 [Note] WSREP: (701dfd2a-
'tcp://
111212 21:06:31 [Note] WSREP:
evs::proto(
34da9138-
34da9138-
111212 21:06:32 [Note] WSREP:
evs::proto(
34da9138-
34da9138-
111212 21:06:32 [Note] WSREP:
evs::proto(
34da9138-
34da9138-
111212 21:06:33 [Note] WSREP:
evs::proto(
34da9138-
34da9138-
111212 21:06:33 [Note] WSREP:
evs::proto(