mariadb

Tree: 0e2d597a59

Author	SHA1	Message	Date
Joerg Bruehe	0e2d597a59	INSTALL-BINARY placeholder (upmerge from 5.1): change invalid URLs (request from Kristofer)	13 years ago
Joerg Bruehe	e00f8f7f3b	INSTALL-BINARY placeholder: change invalid URLs (request from Kristofer)	13 years ago
Tor Didriksen	7c3242d74c	merge 5.1 => 5.5	13 years ago
Tor Didriksen	611484f9a5	Bug#14111180 HANDLE_FATAL_SIGNAL IN PTR_COMPARE_1 / QUEUE_INSERT Space available for merging was calculated incorrectly.	13 years ago
Venkata Sidagam	d9420b9bbb	Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE Null merge from 5.1 to 5.5	13 years ago
Venkata Sidagam	5ecb7db4f9	Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE Fixed the missing of federated/include folder at the time of preparing package distribution, issue happens only in 5.1	13 years ago
Praveenkumar Hulakund	3785ca65f5	Merge from 5.1 to 5.5	13 years ago
Praveenkumar Hulakund	bb64579de8	BUG#13868860 - LIMIT '5' IS EXECUTED WITHOUT ERROR WHEN '5' IS PLACE HOLDER AND USE SERVER-SIDE Analysis: LIMIT always takes nonnegative integer constant values. http://dev.mysql.com/doc/refman/5.6/en/select.html So parsing of value '5' for LIMIT in SELECT fails. But, within prepared statement, LIMIT parameters can be specified using '?' markers. Value for the parameter can be supplied while executing the prepared statement. Passing string values, float or double value for LIMIT works well from CLI. Because, while setting the value for the parameters from the variable list (added using SET), if the value is for parameter LIMIT then its converted to integer value. But, when prepared statement is executed from the other interfaces as J connectors, or C applications etc. The value for the parameters are sent to the server with execute command. Each item in log has value and the data TYPE. So, While setting parameter value from this log, value is set to all the parameters with the same data type as passed. But here logic to convert value to integer type if its for LIMIT parameter is missing. Because of this,string '5' is set to LIMIT. And the same is logged into the binlog file too. Fix: When executing prepared statement having parameter for CLI it worked fine, as the value set for the parameter is converted to integer. And this failed in other interfaces as J connector,C Applications etc as this conversion is missing. So, as a fix added check while setting value for the parameters. If the parameter is for LIMIT value then its converted to integer value.	13 years ago
Venkata Sidagam	2e1f259f74	Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE Merged pb2 test failure fix from mysql-5.1 to mysql-5.5	13 years ago
Venkata Sidagam	c6c8645ae9	Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE Fix for pb2 test failure.	13 years ago
Nirbhay Choubey	0f532388d2	Merge of patch for Bug#13741677 from mysql-5.1.	13 years ago
Nirbhay Choubey	b89363de1d	Bug#13741677 MYSQL_SECURE_INSTALLATION DOES NOT WORK + SAVES ROOT PASSWORD TO DISK! The secure installation scripts connect to the server by storing the password in a temporary option file. Now, if the script gets killed or fails for some reason, the removal of the option file may not take place. This patch introduces following enhancements : * (.sh) Made sure that cleanup happens at every call to 'exit 1'. This is performed implicitly by END{} in pl.in. * (.pl.in) Added a warning in case unlink fails to delete the option/query files. * (.sh/.pl.in) Added more signals to the signal handler list. SIG# 1, 3, 6, 15	13 years ago
Tor Didriksen	da4f2a26ca	merge 5.1 => 5.5	13 years ago
Tor Didriksen	76386edb83	Backport of Bug#14171740 65562: STRING::SHRINK SHOULD BE A NO-OP WHEN ALLOCED=0	13 years ago
Venkata Sidagam	b82414792b	Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE Merged from mysql-5.1 to mysql-5.5	13 years ago
Venkata Sidagam	3b954d1ddd	Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE Problem description: Table 't' created with two colums having compound index on both the columns under innodb/myisam engine at remote machine. In the local machine same table is created undet the federated engine. A select having where clause with along 'AND' operation gives wrong results on local machine. Analysis: The given query at federated engine is wrongly transformed by federated::create_where_from_key() function and the same was sent to the remote machine. Hence the local machine is showing wrong results. Given query "select c1 from t where c1 <= 2 and c2 = 1;" Query transformed, after ha_federated::create_where_from_key() function is: SELECT `c1`, `c2` FROM `t` WHERE (`c1` IS NOT NULL ) AND ( (`c1` >= 2) AND (`c2` <= 1) ) and the same sent to real_query(). In the above the '<=' and '=' conditions were transformed to '>=' and '<=' respectively. ha_federated::create_where_from_key() function behaving as below: The key_range is having both the start_key and end_key. The start_key is used to get "(`c1` IS NOT NULL )" part of the where clause, this transformation is correct. The end_key is used to get "( (`c1` >= 2) AND (`c2` <= 1) )", which is wrong, here the given conditions('<=' and '=') are changed as wrong conditions('>=' and '<='). The end_key is having {key = 0x39fa6d0 "", length = 10, keypart_map = 3, flag = HA_READ_AFTER_KEY} The store_length is having value '5'. Based on store_length and length values the condition values is applied in HA_READ_AFTER_KEY switch case. The switch case 'HA_READ_AFTER_KEY' is applicable to only the last part of the end_key and for previous parts it is going to 'HA_READ_KEY_OR_NEXT' case, here the '>=' is getting added as a condition instead of '<='. Fix: Updated the 'if' condition in 'HA_READ_AFTER_KEY' case to affect for all parts of the end_key. i.e 'i > 0' will used for end_key, Hence added it in the if condition.	13 years ago
Thayumanavar	436c0b04cb	Bug#13699303 - THREAD POOL PLUGIN IGNORES TIMEOUT. PROBLEM: mysql provides a feature where in a session which is idle for a period specified by the wait_timeout variable (whose value is in seconds), the session is closed This feature is not present when we use thread pool. FIX: This patch implements the interface functions which is required to implement the wait_timeout functionality in the thread pool plugin.	13 years ago
Sujatha Sivakumar	a0e448c4d4	Follow up patch for BUG#13961678. Fixing compilation warning given below. "warning: integer constant is too large for 'long' type"	13 years ago
Annamalai Gurusami	11af85aea9	Null merge from mysql-5.1 to mysql-5.5.	13 years ago
Annamalai Gurusami	c65932be49	Bug #13113026 INFORMATION_SCHEMA.INNODB_BUFFER_PAGE_LRUFROM 5.6 BACKPORT Backporting the WL#5716, "Information schema table for InnoDB buffer pool information". Backporting revisions 2876.244.113, 2876.244.102 from mysql-trunk. rb://1175 approved by Jimmy Yang.	13 years ago
Annamalai Gurusami	336a17576c	Bug #13113026 INFORMATION_SCHEMA.INNODB_BUFFER_PAGE_LRUFROM 5.6 BACKPORT Backporting the WL#5716, "Information schema table for InnoDB buffer pool information". Backporting revisions 2876.244.113, 2876.244.102 from mysql-trunk. rb://1177 approved by Jimmy Yang.	13 years ago
Harin Vadodaria	d259fae7e4	Bug#13904906: YASSL PRE-AUTH CRASH WITH 5.1.62, 5.5.22 Problem: Valgrind reports errors when an invalid certificate is used on the client. Solution: Updated yaSSL to version 2.2.2.	13 years ago
Sujatha Sivakumar	f9e6613bd4	Bug#13961678:MULTI-STATEMENT TRANSACTION REQUIRED MORE THAN 'MAX_BINLOG_CACHE_SIZE' ERROR Problem: ======= MySQL returns following error in win64. "ERROR 1197 (HY000): Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again" when user tries to load >4G file even if max_binlog_cache_size set to maximum value. On Linux everything works fine. Analysis: ======== The `max_binlog_cache_size' variable is of type `ulonglong'. This value is set to `ULONGLONG_MAX' at the time of server start up. The above value is stored in an intermediate variable named `saved_max_binlog_cache_size' which is of type `ulong'. In visual c++ complier the `ulong' type is of 4bytes in size and hence the value is getting truncated to '4GB' and the cache is not able to grow beyond 4GB size. The same limitation is observed with "max_binlog_stmt_cache_size" as well. Similar fix has been applied. Fix: === As part of fix the type "ulong" is replaced with "my_off_t" which is of type "ulonglong".	13 years ago
Joerg Bruehe	02565667ac	Fix bug#14318456 SPEC FILE DOES NOT RUN THE TEST SUITE DURING RPM BUILD Add a macro "runselftest" to the spec file for RPM builds. If its value is 1 (the default), the test suite will be run during the RPM build. To prevent that, add this to the rpmbuild command line: --define "runselftest 0" Failures of the test suite will NOT make the RPM build fail!	13 years ago
Alexander Barkov	4541988b69	Merging from 5.1	13 years ago
Alexander Barkov	882e9381cc	Fixing wrong copyright. Index.xml was modified in 2005, while the copyright notice still mentioned 2003.	13 years ago
Ashish Agarwal	01f0aadd6e	BUG#13555854: CHECK AND REPAIR TABLE SHOULD BE MORE ROBUST [1] ISSUE: Incorrect key file. Key file is corrupted, Reading incorrect key information (keyseg) from index file. Key definition in .MYI and .FRM file differs. Starting pointer to read the keyseg information is changed to a value greater than the pack_reclength. Memcpy tries to read keyseg information from unallocated memory which causes the crash. SOLUTION: One more check added to compare the the key definition in .MYI and .FRM file. If the definition differ, server produces an error.	13 years ago
mysql-builder@oracle.com	ec5ecfd584		13 years ago
Bjorn Munch	d23e3ad063	null upmerge	13 years ago
Bjorn Munch	3fb225252a	Reverting broken configure/make stuff	13 years ago
mysql-builder@oracle.com	f666bfc1bd		13 years ago
Bjorn Munch	7a38e06166	upmerge 14035452 5.1 -> 5.5	13 years ago
Bjorn Munch	1a6ce811fd	Bug #14035452 - MODULARIZE MYSQL_CLIENT_TEST Added new minimal client using same framework Added internal test using it Small changes to top level make/configure/cmake to have it built	13 years ago
Venkata Sidagam	e5eacf70a7	Bug #12615411 - server side help doesn't work as first statement Merged from mysql-5.1 to mysql-5.5	13 years ago
Venkata Sidagam	6ee1c03043	Bug #12615411 - server side help doesn't work as first statement Problem description: Giving "help 'contents'" in the mysql client as a first statement gives error Analysis: In com_server_help() function the "server_cmd" variable was initialised with buffer->ptr(). And the "server_cmd" variable is not updated since we are passing "'contents'"(with single quote) so the buffer->ptr() consists of the previous buffer values and it was sent to the mysql_real_query() hence we are getting error. Fix: We are not initialising the "server_cmd" variable and we are updating the variable with "server_cmd= cmd_buf" in any of the case i.e with single quote or without single quote for the contents. As part of error message improvement, added new error message in case of "help 'contents'".	13 years ago
Chaithra Gopalareddy	0e729b5d53	Merge from 5.1 to 5.5	13 years ago
Chaithra Gopalareddy	a56c4692d4	Bug#11762052: 54599: BUG IN QUERY PLANNER ON QUERIES WITH "ORDER BY" AND "LIMIT BY" CLAUSE PROBLEM: When a 'limit' clause is specified in a query along with group by and order by, optimizer chooses wrong index there by examining more number of rows than required. However without the 'limit' clause, optimizer chooses the right index. ANALYSIS: With respect to the query specified, range optimizer chooses the first index as there is a range present ( on 'a'). Optimizer then checks for an index which would give records in sorted order for the 'group by' clause. While checking chooses the second index (on 'c,b,a') based on the 'limit' specified and the selectivity of 'quick_condition_rows' (number of rows present in the range) in 'test_if_skip_sort_order' function. But, it fails to consider that an order by clause on a different column will result in scanning the entire index and hence the estimated number of rows calculated above are wrong (which results in choosing the second index). FIX: Do not enforce the 'limit' clause in the call to 'test_if_skip_sort_order' if we are creating a temporary table. Creation of temporary table indicates that there would be more post-processing and hence will need all the rows. This fix is backported from 5.6. This problem is fixed in 5.6 as part of changes for work log #5558	13 years ago
Nuno Carvalho	1b4523488a	BUG#14310067: RPL_CANT_READ_EVENT_INCIDENT AND RPL_BUG41902 FAIL ON 5.5 rpl_cant_read_event_incident: Slave applies updates from bug11747416_32228_binlog.000001 file which contains a CREATE TABLE t statement and an incident, when SQL thread is running slowly IO thread may reach the incident before SQL thread executes the create table statement. Execute "drop table if exists t" and also perform a RESET MASTER to clean slave binary logs. rpl_bug41902: Error "MYSQL_BIN_LOG::purge_logs was called with file ./master-bin.000001 not listed in the index." suppression is not considering windows path, there is ".\master-bin.000001". Changed suppression to: "MYSQL_BIN_LOG::purge_logs was called with file ..master-bin.000001 not listed in the index", to match ".\" and "./".	13 years ago
Annamalai Gurusami	e231e7f8eb	Merging from mysql-5.1 to mysql-5.5.	13 years ago
Annamalai Gurusami	e612f55237	Bug #11765218 58157: INNODB LOCKS AN UNMATCHED ROW EVEN THOUGH USING RBR AND RC Description: When scanning and locking rows with < or <=, InnoDB locks the next row even though row based binary logging and read committed is used. Solution: In the handler, when the row is identified to fall outside of the range (as specified in the query predicates), then request the storage engine to unlock the row (if possible). This is done in handler::read_range_first() and handler::read_range_next().	13 years ago
hery.ramilison@oracle.com	e7dd7ac58b	Raise version number after cloning 5.5.27	13 years ago
Bjorn Munch	fd784e5ec8	Empty version change upmerge	13 years ago
bjorn.munch@oracle.com	f4fd8bcfae	Raise version number after cloning 5.1.65	13 years ago
mysql-builder@oracle.com	b6e860c8d4		13 years ago
mysql-builder@oracle.com	181fcba45b		13 years ago
Chaithra Gopalareddy	781b05fbad	Bug #13444084:PRIMARY KEY OR UNIQUE KEY >453 BYTES FAILS FOR COUNT DISTINCT GROUP BY PROBLEM: To calculate the final result of the count(distinct(select 1)) we call 'end_send' function instead of 'end_send_group'. 'end_send' cannot be called if we have aggregate functions that need to be evaluated. ANALYSIS: While evaluating for a possible loose_index_scan option for the query, the variable 'is_agg_distinct' is set to 'false' as the item in the distinct clause is not a field. But, we choose loose_index_scan by not taking this into consideration. So, while setting the final 'select_function' to evaluate the result, 'precomputed_group_by' is set to TRUE as in this case loose_index_scan is chosen and we do not have agg_distinct in the query (which is clearly wrong as we have one). As a result, 'end_send' function is chosen as the final select_function instead of 'end_send_group'. The difference between the two being, 'end_send_group' evaluates the aggregates while 'end_send' does not. Hence the wrong result. FIX: The variable 'is_agg_distinct' always represents if 'loose_idnex_scan' can be chosen for aggregate_distinct functions present in the select. So, we check for this variable to continue with loose_index_scan option.	13 years ago
Rohit Kalhans	9689dd1fd2	bug#11759333: follow-up patch for the failure on pb2 windows build	13 years ago
Mayank Prasad	7dcc643d10	Bug#13889741: HANDLE_FATAL_SIGNAL IN _DB_ENTER_ \|HANDLE_FATAL_SIGNAL IN STRNLEN Follow up patch to resolve pb2 failure on windows platform	13 years ago
Jon Olav Hauglid	96bb813a45	Bug#12623923 Server can crash after failure to create primary key with innodb tables The bug was triggered if a single ALTER TABLE statement both added and dropped indexes and ALTER TABLE failed during drop (e.g. because the index was needed in a foreign key constraint). In such cases, the server index information would get out of sync with InnoDB - the added index would be present inside InnoDB, but not in the server. This could then lead to InnoDB error messages and/or server crashes. The root cause is that new indexes are added before old indexes are dropped. This means that if ALTER TABLE fails while dropping indexes, index changes will be reverted in the server but not inside InnoDB. This patch fixes the problem by dropping any added indexes if drop fails (for ALTER TABLE statements that both adds and drops indexes). However, this won't work if we added a primary key as this key might not be possible to drop inside InnoDB. Therefore, we resort to the copy algorithm if a primary key is added by an ALTER TABLE statement that also drops an index. In 5.6 this bug is more properly fixed by the handler interface changes done in the scope of WL#5534 "Online ALTER".	13 years ago
mysql-builder@oracle.com	acc896135e		13 years ago

1 2 3 4 5 ...

70685 Commits (0e2d597a598d352374443953fe356f5688b2d771) All Branches Search

70685 Commits (0e2d597a598d352374443953fe356f5688b2d771)

All Branches