Tags: feverg/mysql
Tags
Reverted the changes to spec file, updated the logic to get the corre… …ct count of PID files --BZR-- revision-id: balasubramanian.kandasamy@oracle.com-20130909174944-0mkvle12gz9ockc7 property-audit-revid: balasubramanian.kandasamy@oracle.com-20130909174944-mu5t6mw8q16xouvu property-branch-nick: mysql-5.5.34-release testament3-sha1: 7cebaa01708fcb605db5463a0dc578dec6cde08d
Empty version change upmerge --BZR-- revision-id: [email protected] property-audit-revid: [email protected] property-branch-nick: mysql-5.5 testament3-sha1: 3bbecb7b7d16e88be43ccdea3cac2a6e58ac4919
Bug#17029399 - CRASH IN ITEM_REF::FIX_FIELDS WITH TRIGGER ERRORS Problem:- In a Procedure, when we are comparing value of select query with IN clause and they both have different collation, cause error on first time execution and assert second time. procedure will have query like set @x = ((select a from t1) in (select d from t2));<---proc1 sel1 sel2 Analysis:- When we execute this proc1(first time) While resolving the fields of user variable, we will call Item_in_subselect::fix_fields while will resolve sel2. There in Item_in_subselect::select_transformer, we evaluate the left expression(sel1) and store it in Item_cache_* object (to avoid re-evaluating it many times during subquery execution) by making Item_in_optimizer class. While evaluating left expression we will prepare sel1. After that, we will put a new condition in sel2 in Item_in_subselect::select_transformer() which will compare t2.d and sel1(which is cached in Item_in_optimizer). Later while checking the collation in agg_item_collations() we get error and we cleanup the item. While cleaning up we cleaned the cached value in Item_in_optimizer object. When we execute the procedure second time, we have condition for sel2 and while setup_cond(), we can't able to find reference item as it is cleanup while item cleanup.So it assert. Solution:- We should not cleanup the cached value for Item_in_optimizer object, if we have put the condition to subselect. --BZR-- revision-id: [email protected] property-audit-revid: [email protected] property-branch-nick: 5.1 testament3-sha1: c3cfa1b74c6e6b6de2b016824659d21b69fd9c00
Removed random passwords feature for Bugfix#17160741 (not applicable … …for 5.5.X) --BZR-- revision-id: balasubramanian.kandasamy@oracle.com-20130715114127-qfk935f9ksh1kpfr property-audit-revid: balasubramanian.kandasamy@oracle.com-20130715114127-1k1s45mxf9j7swtl property-branch-nick: mysql-5.5.33-release testament3-sha1: 6ff2de20d0664361dafeb50a4e271a88bf1ca21e
Bug#17033706 SINCE 5.5.32 & 5.6.12, INNODB CANT START WITH OWN
MULTI-FILE TABLESPACE
ANALYSIS
--------
When a tablespace has multiple data files, InnoDB fails to
open the tablespace. This is because for each ibd file,
the first page is checked.But the first page of all ibd file
need not be the first page of the tablespace. Only the first
page of the tablespace contains the tablespace header. When
we check the first page of an ibd file that is not the first
page of the tablespace, then the "tablespace flags" is not
really available.This was wrongly used to check if a page is
corrupt or not.
FIX
---
Use the tablespace flags only if the page number is 0
in a tablespace.
[Approved by Inaam rb#2836 ]
--BZR--
revision-id: [email protected]
property-audit-revid: [email protected]
property-branch-nick: mysql-5.5
testament3-sha1: 05aa717a9d7de16c692c03ac84c31ef6e25795bd
Bug#58165: "my_empty_string" gets modified and causes LOAD DATA to fa… …il and Cleanup test case (left outfile in data dir) --BZR-- revision-id: [email protected] property-audit-revid: [email protected] property-branch-nick: 5.1 testament3-sha1: 2401d7d7a60d4320583f15e18ff40a2f4d0e3131
Bug#58165: "my_empty_string" gets modified and causes LOAD DATA to fa… …il and Cleanup test case (left outfile in data dir) --BZR-- revision-id: [email protected] property-audit-revid: [email protected] property-branch-nick: 5.1 testament3-sha1: 2401d7d7a60d4320583f15e18ff40a2f4d0e3131
PreviousNext