1 of 19

Changelogs - MariaDB 5.3 Series

MariaDB 5.3 Changelog Series

MariaDB 5.3.12 Changelog

Download | Release Notes | Changelog |Overview of 5.3

Release date: 30 Jan 2013

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3621 [merge] Mon 2013-01-28 09:12:23 +0100
- 5.2 merge
- Mon 2013-01-28 09:10:01 +0100
  - compilation error with -Wuninitialized -Werror
- [merge] Fri 2013-01-25 17:22:21 +0100
  - 5.1 merge
  - Fri 2013-01-25 14:29:46 +0100
    - Server crashes on normal shutdown in closefrm after executing a query from MyISAM table
Sat 2013-01-26 22:33:18 +0100
- Wrong result (missing row) on a DISTINCT query with the same subquery in the SELECT list and GROUP BY
- fix remove_dup_with_hash_index() and remove_dup_with_compare() to take NULLs into account
Fri 2013-01-25 16:56:57 +0200
- The problem was that expression with field after transformation (on the first execution) reached by fix_fields() (via reference) before row which it belongs to (on the second execution) and fix_field for row did not follow usual protocol for Items with argument (first check that the item fixed then call fix_fields).
- Item_row::fix_field fixed.
[merge] Fri 2013-01-25 10:20:45 +0100
- 5.2 merge
- Fri 2013-01-25 10:19:35 +0100
  - Replace deprecated SET OPTION syntax in mysqldump
[merge] Mon 2013-01-21 21:29:19 -0800
- Merge 5.2->5.3
- [merge] Mon 2013-01-21 15:23:40 -0800
  - Merge 5.1->5.2
Wed 2013-01-16 21:07:26 +0200
- fix.
- The problem was that maybe_null of Item_row and its componetes was unsynced after update_used_tables() (and so pushed_cond_guards was not initialized but then requested).
- Fix updates Item_row::maybe_null on update_used_tables().
Thu 2013-01-17 16:08:05 +0200
- Optimizer difference between MySQL and MariaDB with stored functions in WHERE clause of UPDATE or DELETE statements
- Analysis The reason for the less efficient plan was result of a prior design decision - to limit the eveluation of constant expressions during optimization to only non-expensive ones. With this approach all stored procedures were considered expensive, and were not evaluated during optimization. As a result, SPs didn't participate in range optimization, which resulted in a plan with table scan rather than index range scan.
Thu 2013-01-17 13:53:15 +0200
- backport of: Don't reset maybe_null in update_used_tables(); This breaks ROLLUP This fixed failing test in group_by.test
Wed 2013-01-16 15:11:13 +0200
- fix.
- Subquery turned into constant too late to be excluded from grouping list so test for constant added to the create_temp_table().
Fri 2013-01-11 20:26:34 -0800
- Fixed bug . The bug could lead to a wrong estimate of the number of expected rows in the output of the EXPLAIN commands for queries with GROUP BY. This could be observed in the test case for LP bug 934348.
Fri 2013-01-11 12:44:21 +0100
- : Make sure strmov symbol is exported by client library on Linux (even if the server and libraries itself use stpcpy instead of it)
- It is a workaround that allows myodbc built by certain distributions' (CentOS,Fedora) to peacefully coexist with mariadb client libraries. The problem is that MyODBC in these distros needs strmov() to be exported by mysql client shared library, or else myodbc fails to load.
[merge] Thu 2013-01-10 15:40:21 +0100
- 5.2->5.3 merge
- [merge] Thu 2013-01-10 13:54:04 +0100
  - 5.1 merge
Tue 2013-01-08 21:23:03 +0100
- FROM_DAYS() returns different result in MariaDB comparing to MySQL: NULL vs 0000-00-00
- fixed a regression, introduced while fixing
Fri 2012-12-28 14:41:46 +0200
- & & : Wrong result (extra rows) with ALL subquery from a MERGE view.
- The problem was in the lost ability to be null for the table of a left join if it is a view/derived table.
- It hapenned because setup_table_map(), was called earlier then we merged the view or derived.
Wed 2012-12-19 15:56:57 +0200
- : Assertion `example' failed in Item_cache::is_expensive_processor with a 2-level IN subquery
- Analysis: The following call stack shows that it is possible to set Item_cache::value_cached, and the relevant value without setting Item_cache::example.
- #0 Item_cache_temporal::store_packed at item.cc:8395 #1 get_datetime_value at item_cmpfunc.cc:915 #2 resolve_const_item at item.cc:7987 #3 propagate_cond_constants at sql_select.cc:12264 #4 propagate_cond_constants at sql_select.cc:12227 #5 optimize_cond at sql_select.cc:13026 #6 JOIN::optimize at sql_select.cc:1016 #7 st_select_lex::optimize_unflattened_subqueries at sql_lex.cc:3161 #8 JOIN::optimize_unflattened_subqueries at opt_subselect.cc:4880 #9 JOIN::optimize at sql_select.cc:1554
Wed 2012-12-05 21:06:00 +0200
- fix.
- Fixed algorithm of detecting of first real table in view/subquery-in-the-FROM-clase.

MariaDB 5.3.11 Changelog

Download | Release Notes | Changelog |Overview of 5.3

Release date: 29 Nov 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3605 Fri 2012-11-23 13:11:31 +0100
- bump the version to 5.3.11
[merge] Thu 2012-11-22 10:30:39 -0800
- Merge
- Wed 2012-11-21 21:55:04 -0800
  - Fixed LP bug #1002146 (bug ). If the setting of system variables does not allow to use join buffer for a join query with GROUP BY <f1,...> / ORDER BY <f1,...> then filesort is not needed if the first joined table is scanned in the order compatible with order specified by the list <f1,...>.
Sat 2012-11-17 16:50:15 +0100
- - Unexpected warnings "Encountered illegal value '' when converting to DECIMAL" on a query with aggregate functions and GROUP BY
[merge] Tue 2012-11-20 13:57:49 +0100
- Merge ->5.3
- [merge] Tue 2012-11-20 13:40:13 +0100
  - Merge ->5.2.
Mon 2012-11-19 18:17:46 +0200
- Adjust unstable test case.
Mon 2012-11-19 15:38:27 +0200
- Reproducible sub select join crash on 5.3.8 and 5.3.9

MariaDB 5.3.10 Changelog

| |Changelog |

Release date: 13 Nov 2012

For the highlights of this release, see the .

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Sat 2012-11-10 00:10:06 +0200

MariaDB 5.3.9 Changelog

| |Changelog |

Release date: 02 Oct 2012

For the highlights of this release, see the .

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Mon 2012-10-01 15:42:49 +0200

MariaDB 5.3.7 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 4 May 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3516 Wed 2012-05-02 22:02:17 +0200
- update the version number
Thu 2012-05-03 13:14:40 +0500
- Fix for failing gis-precise on Windows.
[merge] Wed 2012-05-02 22:02:06 +0200
- 5.2 merge
- Wed 2012-05-02 22:00:31 +0200
  - update the result file
Wed 2012-05-02 15:23:49 +0200
- implement Item_singlerow_subselect::get_date() to avoid unnecessary date->string->date conversion
Wed 2012-05-02 15:22:47 +0200
- - Server crashes in get_datetime_value
- Create an Item_cache based on item's cmp_type, not result_type in subselect_engine.
- Use result_field in Item_cache_temporal::cache_value(), just like all other Item_cache*::cache_value() do.
[merge] Wed 2012-05-02 17:04:28 +0200
- merge
- Wed 2012-05-02 16:53:02 +0200
  - : Wrong result with LAST_DAY('0000-00-00 00:00:00') IS NULL in WHERE condition
Sun 2012-04-29 18:08:11 +0500
- ST_BUFFER fails with the negative D.
  - Points and lines should disappear if we got negative D.
  - To make it work properly inside the GEOMETRYCOLLECTION, we add the empty operation there.
Thu 2012-04-26 19:21:37 +0200
- - Assertion `0' failed in my_message_sql on UPDATE IGNORE, or unknown error on release build
- Don't send_error at the end of mysql_multi_update() if select failed.
- The error, if there was any, was already sent by mysql_select
Fri 2012-04-27 12:59:17 +0300
- Fix ,
- Analysis:
  - The reason for the wrong result is the interaction between constant optimization (in this case 1-row table) and subquery optimization.
[merge] Mon 2012-04-23 20:37:44 +0200
- merge
- Fri 2012-04-20 21:09:16 +0200
  - - incompatibility in frm in case of VIEWs with non-default ALGORITHM option.
Mon 2012-04-23 09:45:27 +0200
- Install headers required to build external storage plugins
- install all private headers in mysql/private/
Thu 2012-04-19 09:16:30 +0300
- fixed.
- Fixed incorrect type casting which made all fields (except very first) changes to materialized table incorrect.
- Saved list of view/derived table used items after expanding '*'.
Thu 2012-04-19 05:37:16 +0400
- : Wrong result (extra rows) with derived_with_keys+loosescan+semijoin=ON, materialization=OFF
- Part#2: Don't try to construct a LooseScan access on indexes that do not guarantee index-ordered reads.
Thu 2012-04-19 04:50:32 +0400
- BUG#978479: Wrong result (extra rows) with derived_with_keys+loosescan+semijoin=ON, materialization=OFF
- Part#1: make EXPLAIN's plan match the one by actual execution:
- Item_subselect::used_tables() should return the same value irrespectively of whether we're running an EXPLAIN or a SELECT.
[merge] Mon 2012-04-16 23:35:38 +0200
- merge
- [merge] Mon 2012-04-16 23:32:50 +0200
  - merge
[merge] Mon 2012-04-16 17:41:43 +0200
- merge
- [merge] Mon 2012-04-16 15:38:53 +0200
  - merge

MariaDB 5.3.5 Changelog

| |Changelog |

Release date: 29 Feb 2012

For the highlights of this release, see the .

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Tue 2012-02-28 15:41:55 +0100

MariaDB 5.3.12 Changelog

Download | Release Notes | Changelog |Overview of 5.3

Release date: 30 Jan 2013

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3621 [merge] Mon 2013-01-28 09:12:23 +0100
- 5.2 merge
- Mon 2013-01-28 09:10:01 +0100
  - compilation error with -Wuninitialized -Werror
- [merge] Fri 2013-01-25 17:22:21 +0100
  - 5.1 merge
  - Fri 2013-01-25 14:29:46 +0100
    - Server crashes on normal shutdown in closefrm after executing a query from MyISAM table
Sat 2013-01-26 22:33:18 +0100
- Wrong result (missing row) on a DISTINCT query with the same subquery in the SELECT list and GROUP BY
- fix remove_dup_with_hash_index() and remove_dup_with_compare() to take NULLs into account
Fri 2013-01-25 16:56:57 +0200
- The problem was that expression with field after transformation (on the first execution) reached by fix_fields() (via reference) before row which it belongs to (on the second execution) and fix_field for row did not follow usual protocol for Items with argument (first check that the item fixed then call fix_fields).
- Item_row::fix_field fixed.
[merge] Fri 2013-01-25 10:20:45 +0100
- 5.2 merge
- Fri 2013-01-25 10:19:35 +0100
  - Replace deprecated SET OPTION syntax in mysqldump
[merge] Mon 2013-01-21 21:29:19 -0800
- Merge 5.2->5.3
- [merge] Mon 2013-01-21 15:23:40 -0800
  - Merge 5.1->5.2
Wed 2013-01-16 21:07:26 +0200
- fix.
- The problem was that maybe_null of Item_row and its componetes was unsynced after update_used_tables() (and so pushed_cond_guards was not initialized but then requested).
- Fix updates Item_row::maybe_null on update_used_tables().
Thu 2013-01-17 16:08:05 +0200
- Optimizer difference between MySQL and MariaDB with stored functions in WHERE clause of UPDATE or DELETE statements
- Analysis The reason for the less efficient plan was result of a prior design decision - to limit the eveluation of constant expressions during optimization to only non-expensive ones. With this approach all stored procedures were considered expensive, and were not evaluated during optimization. As a result, SPs didn't participate in range optimization, which resulted in a plan with table scan rather than index range scan.
Thu 2013-01-17 13:53:15 +0200
- backport of: Don't reset maybe_null in update_used_tables(); This breaks ROLLUP This fixed failing test in group_by.test
Wed 2013-01-16 15:11:13 +0200
- fix.
- Subquery turned into constant too late to be excluded from grouping list so test for constant added to the create_temp_table().
Fri 2013-01-11 20:26:34 -0800
- Fixed bug . The bug could lead to a wrong estimate of the number of expected rows in the output of the EXPLAIN commands for queries with GROUP BY. This could be observed in the test case for LP bug 934348.
Fri 2013-01-11 12:44:21 +0100
- : Make sure strmov symbol is exported by client library on Linux (even if the server and libraries itself use stpcpy instead of it)
- It is a workaround that allows myodbc built by certain distributions' (CentOS,Fedora) to peacefully coexist with mariadb client libraries. The problem is that MyODBC in these distros needs strmov() to be exported by mysql client shared library, or else myodbc fails to load.
[merge] Thu 2013-01-10 15:40:21 +0100
- 5.2->5.3 merge
- [merge] Thu 2013-01-10 13:54:04 +0100
  - 5.1 merge
Tue 2013-01-08 21:23:03 +0100
- FROM_DAYS() returns different result in MariaDB comparing to MySQL: NULL vs 0000-00-00
- fixed a regression, introduced while fixing
Fri 2012-12-28 14:41:46 +0200
- & & : Wrong result (extra rows) with ALL subquery from a MERGE view.
- The problem was in the lost ability to be null for the table of a left join if it is a view/derived table.
- It hapenned because setup_table_map(), was called earlier then we merged the view or derived.
Wed 2012-12-19 15:56:57 +0200
- : Assertion `example' failed in Item_cache::is_expensive_processor with a 2-level IN subquery
- Analysis: The following call stack shows that it is possible to set Item_cache::value_cached, and the relevant value without setting Item_cache::example.
- #0 Item_cache_temporal::store_packed at item.cc:8395 #1 get_datetime_value at item_cmpfunc.cc:915 #2 resolve_const_item at item.cc:7987 #3 propagate_cond_constants at sql_select.cc:12264 #4 propagate_cond_constants at sql_select.cc:12227 #5 optimize_cond at sql_select.cc:13026 #6 JOIN::optimize at sql_select.cc:1016 #7 st_select_lex::optimize_unflattened_subqueries at sql_lex.cc:3161 #8 JOIN::optimize_unflattened_subqueries at opt_subselect.cc:4880 #9 JOIN::optimize at sql_select.cc:1554
Wed 2012-12-05 21:06:00 +0200
- fix.
- Fixed algorithm of detecting of first real table in view/subquery-in-the-FROM-clase.

MariaDB 5.3.7 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 4 May 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3516 Wed 2012-05-02 22:02:17 +0200
- update the version number
Thu 2012-05-03 13:14:40 +0500
- Fix for failing gis-precise on Windows.
[merge] Wed 2012-05-02 22:02:06 +0200
- 5.2 merge
- Wed 2012-05-02 22:00:31 +0200
  - update the result file
Wed 2012-05-02 15:23:49 +0200
- implement Item_singlerow_subselect::get_date() to avoid unnecessary date->string->date conversion
Wed 2012-05-02 15:22:47 +0200
- - Server crashes in get_datetime_value
- Create an Item_cache based on item's cmp_type, not result_type in subselect_engine.
- Use result_field in Item_cache_temporal::cache_value(), just like all other Item_cache*::cache_value() do.
[merge] Wed 2012-05-02 17:04:28 +0200
- merge
- Wed 2012-05-02 16:53:02 +0200
  - : Wrong result with LAST_DAY('0000-00-00 00:00:00') IS NULL in WHERE condition
Sun 2012-04-29 18:08:11 +0500
- ST_BUFFER fails with the negative D.
  - Points and lines should disappear if we got negative D.
  - To make it work properly inside the GEOMETRYCOLLECTION, we add the empty operation there.
Thu 2012-04-26 19:21:37 +0200
- - Assertion `0' failed in my_message_sql on UPDATE IGNORE, or unknown error on release build
- Don't send_error at the end of mysql_multi_update() if select failed.
- The error, if there was any, was already sent by mysql_select
Fri 2012-04-27 12:59:17 +0300
- Fix ,
- Analysis:
  - The reason for the wrong result is the interaction between constant optimization (in this case 1-row table) and subquery optimization.
[merge] Mon 2012-04-23 20:37:44 +0200
- merge
- Fri 2012-04-20 21:09:16 +0200
  - - incompatibility in frm in case of VIEWs with non-default ALGORITHM option.
Mon 2012-04-23 09:45:27 +0200
- Install headers required to build external storage plugins
- install all private headers in mysql/private/
Thu 2012-04-19 09:16:30 +0300
- fixed.
- Fixed incorrect type casting which made all fields (except very first) changes to materialized table incorrect.
- Saved list of view/derived table used items after expanding '*'.
Thu 2012-04-19 05:37:16 +0400
- : Wrong result (extra rows) with derived_with_keys+loosescan+semijoin=ON, materialization=OFF
- Part#2: Don't try to construct a LooseScan access on indexes that do not guarantee index-ordered reads.
Thu 2012-04-19 04:50:32 +0400
- BUG#978479: Wrong result (extra rows) with derived_with_keys+loosescan+semijoin=ON, materialization=OFF
- Part#1: make EXPLAIN's plan match the one by actual execution:
- Item_subselect::used_tables() should return the same value irrespectively of whether we're running an EXPLAIN or a SELECT.
[merge] Mon 2012-04-16 23:35:38 +0200
- merge
- [merge] Mon 2012-04-16 23:32:50 +0200
  - merge
[merge] Mon 2012-04-16 17:41:43 +0200
- merge
- [merge] Mon 2012-04-16 15:38:53 +0200
  - merge

MariaDB 5.3.2 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 14 Oct 2011

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3231 Thu 2011-10-13 00:15:51 +0400
- Remove garbage comment
Wed 2011-10-12 21:40:56 +0400
- : Crash in add_ref_to_table_cond() when grouping by a PK
- Testcase
Wed 2011-10-12 21:38:40 +0400
- Code cleanup: move variable into branch that uses it
Wed 2011-10-12 14:01:01 +0200
- fix a compilation failure for perl Net::HandlerSocket module
[merge] Wed 2011-10-12 12:45:35 +0200
- merge
- [merge] Wed 2011-10-12 12:30:55 +0200
  - merge
Wed 2011-10-12 14:23:42 +0400
- Fix compile error: ‘cond_copy’ may be used uninitialized in this function.
Wed 2011-10-12 13:19:37 +0400
- : Wrong result with semijoin + materialization + firstmatch + multipart key
- Make advance_sj_state() not to attempt building duplicate removal strategies when we're doing optimization of an SJM-nest.
Wed 2011-10-12 02:04:03 +0400
- Update subselect_sj{,2}_mat.result with changes that were lost when they were deleted and re-created.
Tue 2011-10-11 23:38:26 +0200
- Restore files accidentally deleted in previous merge.
[merge] Tue 2011-10-11 23:52:23 +0400
- Merge: fix subselect_sj2*.test: add missing DROP TABLE statement
  - Tue 2011-10-11 23:48:50 +0400
    Fix testcases from the previous push: add missing DROP TABLE statement
Tue 2011-10-11 21:43:43 +0200
- when freeing a possibly NULL pointer under safemalloc - use MY_ALLOW_ZERO_PTR
[merge] Tue 2011-10-11 20:20:19 +0200
- merge
- [merge] Tue 2011-10-11 20:18:46 +0200
  - merge
[merge] Tue 2011-10-11 21:57:57 +0400
- Merge fix for BUG#869012
- Tue 2011-10-11 21:34:00 +0400
  - : Wrong result with semijoin + materialization + AND in WHERE
[merge] Tue 2011-10-11 12:55:42 +0200
- merge
- [merge] Mon 2011-10-10 19:34:37 +0200
  - merge
Tue 2011-10-11 02:36:08 -0700
- Fixed .
- This bug is a consequence of the fix in the function add_ref_to_table_cond for that turned out to be not quite correct: it tried to AND the same generated condition with two different other conditions.
- This patch creates a copy of the generated condition if the condition needs to be ANDed with two different items.
[merge] Mon 2011-10-10 23:34:32 +0300
- Merge
- Wed 2011-10-05 18:18:00 +0300
  - Making subquery cache on by default.
Mon 2011-10-10 15:38:11 +0200
- remove unnecessary define
Thu 2011-09-29 20:12:57 +0200
- make sure that cast(... as date) returns a valid date, as specified by the caller.
- make Item::send() request a date according to the current SQL mode limitations.
[merge] Thu 2011-10-06 01:21:15 +0400
- Merge fix for BUG#860580
- Thu 2011-10-06 01:11:08 +0400
  - : Sporadic crash / valgrind warning in register_field_in_read_map() with semijoin
[merge] Wed 2011-10-05 16:56:17 +0300
- Automatic merge with 5.2
- [merge] Wed 2011-10-05 16:53:35 +0300
  - Automatic merge with 5.1
[merge] Wed 2011-10-05 16:15:30 +0300
- Automatic merge
- Wed 2011-10-05 15:59:49 +0300
  - Fixed "Periodic aria checkpoints prevent power management"
Tue 2011-10-04 23:57:46 +0300
- Fix
- Analysis:
  - The cause of the bug was that the method subselect_rowid_merge_engine::partial_match() was not designed for re-execution within the same query. Specifically, it didn't cleanup the bitmap of matching keys after completion.
Tue 2011-10-04 12:00:55 -0700
- Made the result test of a test case platform independent
- (correction for the previous patch).
Tue 2011-10-04 08:45:01 -0700
- Made the result test of a test case platform independent.
Mon 2011-10-03 21:36:18 -0700
- Fixed a bad merge.
- Changed a test case to make its result set platform independent.
[merge] Mon 2011-10-03 15:50:42 -0700
- Merge.
- Fri 2011-09-30 21:53:59 -0700
  - The previous correction of the cost estimate to access a joined table in the function best_access_path revealed another bug: currently table scans on NULL keys used for NOT IN subqueries cannot work together with employment of join caches for inner tables of these subqueries. Otherwise the result can be wrong as it could be seen with the result of the test case constructed for bug #37894 in the file subselect3_jcl6.result.
[merge] Tue 2011-10-04 02:24:04 +0400
- Merge
- Tue 2011-10-04 02:20:06 +0400
  - Fix buildbot failure in previous fix ():
Mon 2011-10-03 22:48:15 +0300
- Fix
- Analysis:
  - The cause of the bug was the changed meaning of subselect_partial_match_engine::has_covering_null_row. Previously it meant that there is row with NULLs in all nullable fields of the materialized subquery table. Later it was changed to mean a row with NULLs in all fields of this table.
[merge] Sat 2011-10-01 00:56:42 +0400
- Merge
- Sat 2011-10-01 00:55:57 +0400
  - : Assertion `fixed == 1' failed in Item_func_eq::val_int() with semijoin + materialization
[merge] Sat 2011-10-01 00:20:01 +0400
- Merge
- Sat 2011-10-01 00:10:03 +0400
  - : Crash in create_ref_for_key with semijoin + materialization
[merge] Thu 2011-09-29 17:07:43 +0400
- Merge
- Thu 2011-09-29 17:03:12 +0400
  - : Assertion `keypart_map' failed in mi_rkey with semijoin
Thu 2011-09-29 12:58:20 +0200
- Fix test suite:
  - on Windows, kill can and almost always will return client error 2013 ("Lost connection...") on the killed connection,
  - On the server side, if connection is "sleeping" KILL will close the socket, thus socket error on client is expected.
Wed 2011-09-28 17:20:43 +0300
- Fix .
- Analysis:
  - The crash is a result of the same cause as all similar bugs (, , , ,). The general pattern is that some optimization requires the evaluation of some condition (e.g. the WHERE clause), and this condition contains a subquery, such that the subquery itself requires a temporary table for its execution. During the subquery execution the original tables in the FROM clause are replaced by the temporary table needed for the final GROUP or ORDER operation. All this happens during optimization of the outer query. Later when EXPLAIN is run for the subquery, explain attempts to print the name of the tables in the FROM clause, but it finds there a temporary table without a corresponding TABLE_LIST object. The attempt to print the name of a NULL table list results in a crash.
[merge] Wed 2011-09-28 13:01:47 +0400
- Merge
- Wed 2011-09-28 12:58:01 +0400
  - : Second crash with get_fanout_with_deps() with semijoin + materialization
Tue 2011-09-27 17:40:04 +0300
- Fixed test case that changed when max_user_connections was made signed. Threat ER_CONNECTION_KILLED same as ER_SERVER_SHUTDOWN in replication (to get rid of a possible warning in error log)
[merge] Mon 2011-09-26 23:54:00 +0300
- Automatic merge
- Mon 2011-09-26 20:26:47 +0300
  - Allow one to block an account by using GRANT max_user_connections = -1
[merge] Mon 2011-09-26 14:15:04 +0400
- Merge
- Mon 2011-09-26 13:56:09 +0400
  - : Wrong result with semijoin + loosescan + comma join
Sat 2011-09-24 14:45:49 +0200
- portability fix: use SOCKET_SIZE_TYPE in the handlersocket plugin
Fri 2011-09-23 12:00:52 +0200
- fix typo: binlog_annotate_rows_events -> binlog_annotate_row_events
[merge] Fri 2011-09-23 01:30:44 +0400
- Merge
- Fri 2011-09-23 01:25:08 +0400
  - : Wrong result with semijoin + "Impossible where"
Thu 2011-09-22 11:04:00 +0200
- portability fix: avoid anonymous structs and unions in C
Thu 2011-09-22 01:55:17 +0400
- Fix after previous cset: update test results
[merge] Tue 2011-09-20 20:43:57 +0400
- Merge
- Tue 2011-09-20 20:40:07 +0400
  - : Wrong result with second execution of prepared statement with semijoin + view
[merge] Sat 2011-09-17 23:58:36 +0400
- Merge
- Sat 2011-09-17 23:53:50 +0400
  - LPBUG849717: Crash in Item_func::fix_fields on second execution of a prepared statement with semijoin
[merge] Fri 2011-09-16 18:26:20 +0200
- merge
- Fri 2011-09-16 18:15:04 +0200
  - Fix path lookup for singtool
[merge] Thu 2011-09-15 17:25:37 +0300
- Merge with 5.2
- Thu 2011-09-15 16:56:06 +0300
  - Fixed race condition that could cause diff to fail.
branch nick: maria-5.3 Thu 2011-09-15 16:36:43 +0300
- Removed duplicate test
[merge] Wed 2011-09-14 12:43:29 +0400
- Merge
- Tue 2011-09-13 23:45:02 +0400
  - : Wrong result with jkl = 7, BKA, ICP in maria-5.3 + compound index
[merge] branch nick: maria-5.3 Sat 2011-09-10 18:01:27 +0300
- Merge with 5.2
- [merge] Sat 2011-09-10 09:37:55 +0300
  - Automatic merge

MariaDB 5.3.6 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 9 Apr 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3500 Sat 2012-04-07 17:27:00 -0700
- Fixed properly.
- The previous patch for the bug (that erroneously identified the bug as bug 972973 in its comment) was incorrect.
- It turned out that the code that triggered the abort complain reported for the bug was not needed at all.
Sat 2012-04-07 02:29:04 -0700
- Fixed .
- When the function free_tmp_table deletes the handler object for a temporary table the field TABLE::file for this table should be set to NULL. Otherwise an assertion failure may occur.
[merge] Fri 2012-04-06 16:40:39 -0700
- Merge.
- Fri 2012-04-06 15:08:09 -0700
  - Fixed .
Fri 2012-04-06 13:18:12 +0300
- Unused method removed.
[merge] Fri 2012-04-06 14:24:00 +0500
- merging.
- [merge] Fri 2012-04-06 13:51:42 +0500
  - merging.
[merge] Thu 2012-04-05 23:07:18 +0200
- merge
- [merge] Thu 2012-04-05 12:01:52 +0200
  - merge
Thu 2012-04-05 23:32:57 +0300
- Fix of .
- When a view/derived table is converted from merged to materialized the items from the used_item lists are substituted for items referring to the fields of the result of the materialization. The problem appeared with queries employing natural joins. Since the resolution of a natural join was performed only once the used_item list formed at the second execution of the query lacked the references to the fields that were used only in the equality predicates generated for the natural join.
Wed 2012-04-04 21:35:34 +0400
- Make test results stable.
[merge] Wed 2012-04-04 14:19:46 +0300
- Merge with 5.2
- Fixed additional changed pbxt test cases
- [merge] Wed 2012-04-04 13:50:24 +0300
[merge] Wed 2012-04-04 12:37:46 +0400
- Merge
- Wed 2012-04-04 12:26:36 +0400
  - : better comments and function names.
[merge] Wed 2012-04-04 01:00:23 +0300
- Merge with 5.2
- [merge] Wed 2012-04-04 00:33:02 +0300
  - Merge with 5.1
Tue 2012-04-03 15:42:26 +0300
- Don't disable core on signal just becasue platform doesn't handle stack traces
[merge] Mon 2012-04-02 17:54:33 +0200
- merge
- Mon 2012-04-02 11:29:28 +0200
  - SET PASSWORD in 5.2 does not update user's auth plugin
[merge] Mon 2012-04-02 12:27:15 +0300
- automatic merge
- Mon 2012-04-02 11:45:07 +0300
- Fixed "[PATCH] plugin boolean result"
[merge] Fri 2012-03-30 16:13:41 +0200
- merge
- [merge] Fri 2012-03-30 16:12:21 +0200
  - merge
[merge] Fri 2012-03-30 13:54:33 +0300
- Merge from 5.2
- [merge] Fri 2012-03-30 13:51:16 +0300
  - Automatic merge
[merge] Fri 2012-03-30 08:49:57 +0200
- merge
- [merge] Thu 2012-03-29 21:15:30 +0200
  - merge
Thu 2012-03-29 16:32:35 +0200
- remove race conditions from the test
Thu 2012-03-29 21:58:40 +0200
- Add missing include (fixes compile failure with gcc 4.7).
[merge] Wed 2012-03-28 13:58:14 +0300
- Automatic merge
- [merge] Wed 2012-03-28 13:49:07 +0300
- Merge with 5.1
Tue 2012-03-27 16:06:00 +0300
- Added feature request from "Feature request - prevent truncating query in mytop"
- Added feature request 'reading of my.cnf files' to mytop
- Thanks to Jean Weisbuch for the patch/suggestion.
Tue 2012-03-27 14:43:26 +0400
- : Server crashes in embedding_sjm on a simple 1-table select with AND and OR
  - This is a regession introduced by fix for
  - The problem was that there were scenarios where check_simple_equality() would create an Item_equal object but would not call item_equal->set_context_field() on it.
[merge] Mon 2012-03-26 21:38:24 +0400
- Merge
- Mon 2012-03-26 21:34:24 +0400
  - : Wrong result (missing rows) with semijoin+firstmatch, IN/ANY subquery
Mon 2012-03-26 16:06:42 +0300
- Bug fix for "auto_increment_offset != 1 + innodb_autoinc_lock_mode=1 => bulk inserts fail"
- Patch and test case by Patryk Pomykalski
Mon 2012-03-26 15:05:50 +0300
- Sorted some test results that can be different on different machines
Mon 2012-03-26 13:29:45 +0300
- Fixed "Assertion `lock_type != TL_UNLOCK && (lock_type == TL_IGNORE || file->lock.type == TL_UNLOCK)' failed in ha_maria::store_lock with DML, triggers, views"
[merge] Mon 2012-03-26 13:52:55 +0400
- Merge
- Mon 2012-03-26 13:47:00 +0400
  - : Wrong result (missing rows) with semijoin+materialization, IN subquery, InnoDB, TEMPTABLE view
Mon 2012-03-26 11:46:01 +0300
- Increased version number
Sun 2012-03-25 18:31:35 +0400
- : Assertion `0' failed in QUICK_INDEX_SORT_SELECT::need_sorted_output()
- The problem was that
  - we've picked a LooseScan that used full index scan (tab->type==JT_ALL) on certain index.
Sat 2012-03-24 17:08:59 +0100
- Improve filesort performance for small sorts: Don't write pointers to records that we will never use.
Fri 2012-03-23 18:22:39 +0200
- Speedup:
  - Don't call update_virtual_fields() if table->vfield is not set
  - Don't prealloc memory for in open_tables() as this is very seldom used.
Fri 2012-03-23 18:18:16 +0200
- Fixes "JOIN constructors takes a long time in 5.3"
  - Remove all references of MAX_TABLES from JOIN struct and make these dynamic
  - Updated Join_plan_state to allocate just as many elements as it's needed
Fri 2012-03-23 18:11:29 +0200
- Speedups:
  - Optimize away calls to hp_rec_hashnr() by cashing hash
  - Try to get more rows / block (to minimize overhead of HP_PTRS) in HEAP tables.
Thu 2012-03-22 19:56:17 -0700
- Fixed .
- If the first component of a ref key happened to be a constant appeared after constant row substitution then no store_key element should be created for such a component. Yet create_ref_for_key() erroneously could create such an element that caused construction of invalid ref keys and wrong results for some joins.
[merge] Thu 2012-03-22 13:23:55 +0100
- Automerge.
- Thu 2012-03-22 13:21:15 +0100
  - Backport some simple performance patches from 5.5.
[merge] Wed 2012-03-21 19:15:29 +0100
- merge
- [merge] Wed 2012-03-21 18:30:34 +0100
  - merge
Wed 2012-03-21 10:59:20 +0100
- SHOW TABLES was unnecessary opening .frm files
- mark the corresponding I_S table as OPTIMIZE_I_S_TABLE, to let the I_S optimizer figure out whether files need to be opened, and don't open the tables unless I_S optimizer says so.
[merge] Wed 2012-03-21 11:18:20 +0400
- Merge
- Sun 2012-03-18 23:58:20 +0400
  - : Server crashes on 2nd execution of PS in find_field_in_tables with semijoin+materialization
Tue 2012-03-20 17:03:28 -0700
- Fixed .
- This bug in the constructor SEL_IMERGE::SEL_IMERGE could cause huge excessive memory requests.
Mon 2012-03-19 01:04:55 +0400
- : Server crashes in Item_field::fix_after_pullout on INSERT .. SELECT
- Take into account that there may exist Item_field objects with context==NULL.
[merge] Wed 2012-03-14 13:58:18 +0200
- Merge 5.2->5.3
- Wed 2012-03-14 12:09:03 +0200
  - test suite for LP bug#694450
[merge] Tue 2012-03-13 13:49:18 -0700
- Merge.
- Tue 2012-03-13 13:34:20 -0700
  - Fixed .
Tue 2012-03-13 16:38:43 +0200
- Fixed bug "Archive table corruption crashing MariaDB signal 11"
- Added 'from_end' as extra parameter to Field::unpack() to detect wrong from data.
- Change ha_archive::unpack_row() to detect wrong field lengths.
[merge] Mon 2012-03-12 18:21:14 +0400
- Merge
- [merge] Mon 2012-03-12 18:08:40 +0400
  - Merge
Mon 2012-03-12 18:20:30 +0400
- Better comments
[merge] Mon 2012-03-05 22:33:46 -0800
- Merge.
- Mon 2012-03-05 20:32:28 -0800
  - Fixed .
[merge] Mon 2012-03-05 22:00:24 +0200
- Automatic merge
- Mon 2012-03-05 21:59:00 +0200
  - Ensure that we mark all processed tables as 'properly closed'.
Mon 2012-03-05 15:48:12 +0200
- Fix for
- Problem is that subquery execution can't be called during prepare/optimize phase.
- Also small fix for subquery test suite.
Sun 2012-03-04 22:38:17 -0800
- Fixed .
- This bug in the function JOIN::drop_unused_derived_keys() could leave the internal structures for a materialized derived table in an inconsistent state. This led to a not quite correct EXPLAIN output when no additional key had been created to access the table.
- It also may lead to more serious consequences: so, the test case added with this fix caused a crash in mariadb-5.5.20.
Wed 2012-02-29 23:28:16 -0800
- Fixed .
- This bug appeared after the patch for that in the function merge_key_fields forgot to reset a proper value for the val field in the result of the merge operation of the key field created for a regular key access and the key field created to look for a NULL key.
- Adjusted the results of the test case for bug 939009 that actually were incorrect.

MariaDB 5.3.0 Changelog p3

Download |Release Notes |Changelog (page:1 2 3 4 5 6 ) |Overview of 5.3

Release date: 26 July 2011

Revision #3000 [merge] Thu 2011-05-19 20:03:33 -0700
- Merge
- [merge] Thu 2011-05-19 20:01:43 -0700
  - Merged the fix for into 5.3.
    Thu 2011-05-19 18:28:38 -0700
    Fixed
[
- merge] Fri 2011-05-20 01:41:07 +0200
- merge
[merge] Thu 2011-05-19 19:23:06 +0300
- Automatic merge
- Thu 2011-05-19 18:14:02 +0300
  - Updated comments as part of code review
Thu 2011-05-19 08:45:06 +0300
- PBXT test fix.
[merge] Wed 2011-05-18 23:03:46 +0300
- automatic merge
- Wed 2011-05-18 16:27:19 +0300
  - Rewritten patch of percona - switching query cache on and off, removing comments.
[merge] Wed 2011-05-18 15:31:20 +0200
- automerge
- Wed 2011-05-18 15:22:56 +0200
  - merge some fixes for rpl_corruption.test from MySQL 5.6.
[merge] Wed 2011-05-18 15:19:18 +0200
- automerge
Wed 2011-05-18 12:28:17 +0200
- Fix compile warning.
Wed 2011-05-18 00:47:56 +0300
- Removed some alias warnings
- Fixed alias bug when compiling with gcc 4.2.4 that caused subselect.test to fail
Mon 2011-05-16 16:21:09 +0300
- fix dynco test on Windows, really now (from Wlad)
Mon 2011-05-16 16:13:34 +0300
- Fix of compiler errors.
[merge] Mon 2011-05-16 15:16:48 +0300
- Automatic merge
- [merge] Mon 2011-05-16 15:07:04 +0300
  - Merge with 5.3 main
Fri 2011-05-13 18:27:43 +0300
- Directories with .dylib files added to DYLD_LOIBRARY_PATH to allow plugins to use them.
Thu 2011-05-12 18:01:36 +0300
- Fix library build on mac (prevent handlersocket.so loading failure if it called from build directory)
[merge] Thu 2011-05-12 01:02:55 +0300
- Automatic merge with
[merge] Wed 2011-05-11 08:52:16 +0100
- Merge fix for
[merge] Wed 2011-05-11 08:28:11 +0200
- automerge
- Wed 2011-05-11 08:16:49 +0200
  - Fix race in testcase innodb_plugin.group_commit_no_optimize_thread
[merge] Tue 2011-05-10 18:28:05 +0300
- - Automatic merge with 5.3
- Thu 2011-05-05 15:24:28 +0300
  - Fix
Sun 2011-05-08 13:26:07 +0300
- Fixed compiler warnings
[merge] Sat 2011-05-07 15:48:45 +0200
- Merge into main .
- [merge] Thu 2011-05-05 16:35:02 +0200
  - : Merge bugfix from 5.2 to 5.3 codebase + really fix version from which mariadb supports binlog checksums.
Wed 2011-05-04 18:08:44 -0700
- Fixed . If the value of the flag cond_false of an Item_equal object is true then the print method must return the string '0'.
Wed 2011-05-04 11:23:29 -0700
- Fixed : The third parameter in the call of make_cond_for_table() that built the pushed condition containing only outer references was incorrect. This condition appeared for the first time in the patch fixing .
Tue 2011-05-03 17:11:45 -0700
- Fixed : The bug was introduced by the patch that fixed .
Mon 2011-05-02 13:02:36 +0200
- Shoot in the dark - try to fight build environment based on cygwin, where presumably neither TMP nor TEMP environment variable are set.
Mon 2011-05-02 13:25:53 +0300 (no message)
[merge] Fri 2011-04-29 19:20:46 -0700
- Merge
- Wed 2011-04-27 15:29:46 -0700
  - Fixed : The function test_quick_select by mistake did not update the value of table->quick_condition_rows for index intersection scans though the specification explicitly required to do so from any table access plan once the plan provided a better upper bound for the number of rows selected from the table. It resulted in a bogus, usually very big number saved as the cost of the table access. This, in its turn, in many cases forced the optimizer to make a bad choice of the execution plan for join queries.
Thu 2011-04-28 19:56:10 +0300
- Added ALTER ONLINE TABLE, which will give an error if the change can't be done 'instantly' (without a table copy)
Thu 2011-04-28 18:02:26 +0300
- Added option "AND DISABLE CHECKPOINT" to "FLUSH TABLES WITH READ LOCK"
- This makes it possible to do safe multi volume snapshots as long as one snapshots the volume with the transaction logs last.
[merge] Tue 2011-04-26 21:11:06 -0700
- Merge
- Tue 2011-04-26 19:58:41 -0700
  - Fixed , :
Wed 2011-04-20 15:30:21 -0700
- Fixed . In some cases the field max_part_no of the SEL_ARG structure was not initialized. That triggered a Valgrind complain.
Tue 2011-04-19 14:34:40 +0200
- Handlersocket does not load
  - -fimplicit-termplates must be in CXXFLAGS not in handlersocket_la_CXXFLAGS. otehrwise automake puts it in the command line too early to override global -fno-implicit-templates
[merge] Thu 2011-04-14 13:25:18 +0200
- Merge test case fix from -rpl into 5.3.
- Thu 2011-04-14 13:23:02 +0200
  - Fix race in testcase innodb_plugin.group_commit
Tue 2011-04-12 15:06:09 +0200
- Missing PBXT result file updates after previous patch.
[
- merge] Sun 2011-04-10 23:00:08 -0700
- merge
[merge] Fri 2011-04-08 09:39:33 +0200
- Merge various replication-related patches into :
  - Group commit
  - Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT
[merge] Fri 2011-04-08 02:54:01 +0200
- merge
- [
  - merge] Fri 2011-04-08 02:51:56 +0200
Fri 2011-04-08 02:12:03 +0400
- : Wrong results for a subquery with 'semijoin=on'
  - Let advance_sj_state() save the value of JOIN::cur_dups_producing_tables in POSITION::prefix_dups_producing_tables, and restore_sj_state() restore it.
[merge] Mon 2011-04-04 12:38:08 +0400
- Merge: Make EXPLAIN better at displaying MRR/BKA
- Mon 2011-04-04 12:32:52 +0400
  - Amend the previous cset:
[merge] Sun 2011-04-03 21:03:31 +0200
- null merge
Fri 2011-04-01 12:04:59 +0300
- Fixed compiler warnings
[merge] Thu 2011-03-31 18:35:57 +0300
- Automatic merge
- Thu 2011-03-31 18:30:05 +0300
  - Fixed unlikely reference to freed memory in item->print().
[merge] Wed 2011-03-30 23:34:48 +0200
- merge
[merge] Wed 2011-03-30 00:48:35 +0300
- Merge the fix for .
- Mon 2011-03-28 12:55:36 +0300
  - Fix
[
- merge] Tue 2011-03-29 22:43:35 +0200
- merge
Tue 2011-03-29 20:56:54 +0200
- Suppress ANALYZE_TABLE output, to be consistent with rest of the test case
Tue 2011-03-29 20:37:30 +0200
- Fix formatting error message (invalid table name) in handler tests.
[merge] Mon 2011-03-28 17:19:40 +0200
- null merge
[
- merge] Mon 2011-03-28 17:13:41 +0200
- merge
[
- merge] Mon 2011-03-28 12:57:52 +0200
- merge
[
- merge] Mon 2011-03-28 02:04:43 +0200
- merge
[
- merge] Mon 2011-03-28 01:10:55 +0200
- merge
[
- merge] Sat 2011-03-26 00:15:33 +0100
- merge
Fri 2011-03-25 16:33:17 +0300
- : Update test results in pbxt test suite
[merge] Fri 2011-03-25 12:47:44 +0300
- Merge in fix for
- Fri 2011-03-25 12:43:32 +0300
  - Wrong result with OR + NOT NULL in maria-5.3
Thu 2011-03-24 16:34:06 +0200
- Fix
  - Analysis:
    A query with implicit grouping is one with aggregate functions and no GROUP BY clause. MariaDB inherits from MySQL an SQL extenstion that allows mixing aggregate functions with non-aggregate fields. If a query with such mixed select clause produces an empty result set, the meaning of aggregate functions is well defined - either NULL (MIN, MAX, etc.), or 0 (count(*)). However the non-aggregated fields must also have some value, and the only reasonable value in the case of empty result is NULL.

Changelog — page: 3

MariaDB 5.3.0 Changelog p2

Download |Release Notes |Changelog (page:1 2 3 4 5 6 ) |Overview of 5.3

Release date: 26 July 2011

Revision #3069 Wed 2011-06-29 16:05:16 -0700
- Fixed Bug #803410. Due to this bug in the function generate_derived_keys_for_table some key definitions to access materialized derived tables or materialized views were constructed with invalid info for their key parts. This could make the server crash when it optimized queries using materialized derived tables or materialized views.
[merge] Tue 2011-06-28 19:56:30 -0700
- Merge.
- Tue 2011-06-28 18:31:54 -0700
  - Fixed . This crashing bug could manifest itself at execution of join queries over materialized derived tables with IN subquery predicates in the where clause. If for such a query the optimizer chose to use duplicate weed-out with duplicates in a materialized derived table and chose to employ join cache the execution could cause a crash of the server. It happened because the JOIN_CACHE::init method assumed that the value of TABLE::file::ref is set at the moment when the method was called for the employed join cache. It's true for regular tables, but it's not true for materialized derived tables that are filled now at the first access to them, i.e. after the JOIN_CACHE::init has done its job.
Tue 2011-06-28 15:48:44 +0300
- Fixed
  - Analysis:
    The failed assert ensured that the choice of subquery strategy is performed only for queries with at least one table. If there is a LIMIT 0 clause all tables are removed, and the subquery is neither optimized, nor executed during actual optimization. However, if the query is EXPLAIN-ed, the EXPLAIN execution path doesn't remove the query tables if there is a LIMIT 0 clause. As a result, the subquery optimization code is called, which violates the ASSERT condition.
Tue 2011-06-28 11:11:26 +0400
- : Valgrind warning / sporadic crash in evaluate_join_record sql_select.cc:14099 with semijoin
  - Added testcase. The bug is most likely fixed by code.
[merge] Mon 2011-06-27 23:36:20 -0700
- Merge
- Mon 2011-06-27 23:07:46 -0700
  - Fixed . The function create_view_field in some cases incorrectly set the maybe_null flag for the returned items.
[merge] Tue 2011-06-28 00:18:42 +0300
- Automatic merge
- [merge] Tue 2011-06-28 00:13:22 +0300
  - Automatic merge
Mon 2011-06-27 23:38:56 +0400
- Added TODO comments
Sun 2011-06-26 21:55:32 -0700
- Fixed . Ensured valid calculations of the estimates stored in JOIN_TAB::used_fieldlength.
Sat 2011-06-25 14:02:27 -0700
- Fixed . Made mergeable views and mergeable derived tables transparent for the MIN/MAX optimization.
Fri 2011-06-24 21:18:20 -0700
- Added test cases for and fixed by the patch for .
Fri 2011-06-24 18:42:14 -0700
- Fixed . The following were missing in the patch for mwl106:
  - KEY_PART_INFO::fieldnr were not set for generated keys to access tmp tables storing the rows of materialized derived tables/views
  - TABLE_SHARE::column_bitmap_size was not set for tmp tables storing the rows of materialized derived tables/views.
Fri 2011-06-24 14:38:53 -0700
- Fixed . If a view/derived table is non-mergeable then the definition of the tmp table to store the rows for it is created at the prepare stage. In this case if the view definition uses outer joins and a view column belongs to an inner table of one of them then the column should be considered as nullable independently on nullability of the underlying column. If the underlying column happens to be defined as non-nullable then the function create_tmp_field_from_item rather than the function create_tmp_field_from_field should be employed to create the definition of the interesting column in the tmp table.
[merge] Fri 2011-06-24 21:43:31 +0400
- Merge 5.2 -> 5.3 (testcase for now crashes)
Thu 2011-06-23 22:12:22 -0700
- Fixed a valgrind problem. The function setup_tables should handle table_list elements for semijoin materialized tables in a special way when executing a prepared statement for the second time.
Thu 2011-06-23 14:48:45 -0700
- Fixed . The function simple_pred did not take into account that a multiple equality could include ref items (more exactly items of the class Item_direct_view_ref). It caused crashes for queries over derived tables or views if the min/max optimization could be applied to these queries.
[merge] Tue 2011-06-21 18:17:28 -0700
- Merge
- Tue 2011-06-21 18:00:58 -0700
  - Fixed .
Tue 2011-06-21 23:01:01 +0300
- Removed forgotten EXPLAIN EXTENDED from the test file.
[merge] Tue 2011-06-21 16:00:41 +0300
- Automerged with 5.3.
- Tue 2011-06-21 15:50:07 +0300
Fri 2011-06-17 23:00:26 +0200
- - fix missing alpha/beta etc in MSI and ZIP package names.
[merge] Fri 2011-06-17 17:45:41 +0400
- Merge fix for .
- Wed 2011-06-15 18:37:01 +0400
  - : Crash in hp_movelink with Aria engine and subqueries -In do_sj_dups_weedout(), set nulls_ptr to point to NULL bytes (and not to length bytes) of the DuplicateWeedout column.
[merge] Wed 2011-06-15 21:48:38 -0700
- Merge of mwl #106 into 5.3.
- Thu 2011-06-09 12:43:28 -0700
  - Fixed .
Wed 2011-06-15 17:40:18 +0400
- : Update .result file
Wed 2011-06-15 16:02:32 +0400
- : partition.test produces valgrind errors in 5.3-based branches
  - Testcase
Wed 2011-06-15 15:32:24 +0400
- : InnoDB: Error: row_search_for_mysql() is called without ha_innobase::external_lock() in maria-5.3
  - Testcase
Wed 2011-06-15 13:43:04 +0400
- Assertion `!table->file || table->file->inited == handler::NONE' failed with subquery
  - Add testcase
Tue 2011-06-14 18:45:14 +0200
- fix for cast of negative numbers to datetime
Sun 2011-06-12 11:28:22 +0200
- a couple of fixes for pbxt tests
Tue 2011-06-14 15:21:54 +0200
- Another attempt at fixing the rare random failures of rpl_corruption
- The previous patch partially fixed things by waiting for the old dump thread on the master to exit before injecting the DBUG error. This prevents the error injection going to the wrong thread.
- However, there is still the problem that the old dump thread may never exit, causing the wait to time out. This happens if the dump thread manages to write all events down the socket before the socket is closed by the slave. The master dump thread only checks for slave gone when writing a new event, so if no new events are generated, old dump threads can hang around forever on the master after the slave disconnects.
Mon 2011-06-13 12:41:19 +0400
- Remove redundant code that is a result of a wrong merge. (Changeset sp1r-igor@olga.mysql.com-20070526173301-38848 moved this loop from one place to another, then the merge of sp1r-gshchepa/uchum@gleb.loc-20070527192244-26330 have kept both copies).
Sun 2011-06-12 00:35:53 +0400
- In make_join_select():
  - move attempt to evaluate join->exec_const_cond() out of the "Extract constant part of each ON expression" loop (it got there by mistake when merging).
[merge] Sat 2011-06-11 12:04:42 +0300
- Merge with Sergei's tree to get in latest microsecond patches and also fixes to innodb_plugin.
- Fri 2011-06-10 21:15:13 +0200
  - more buildbot fixes
Sat 2011-06-11 11:41:46 +0300
- Fixed build failures with maria3.test and widows build
[merge] Sat 2011-06-11 11:09:17 +0300
- Merge with main 5.3
- [merge] Fri 2011-06-10 12:09:21 +0300
  - Merge with 5.2
Fri 2011-06-10 12:45:43 +0400
- : does not trigger with non-comma joins
  - Add a testcase (the bug has already been fixed)
Fri 2011-06-10 12:36:06 +0400
- [No BUG#] end_tab_idx==-1 passed as parameter to JOIN::get_partial_cost_and_fanout()
  - Handle the case when the subquery's join is degenerate and so has zero tables.
Thu 2011-06-09 21:39:31 +0300
- Removed depricated --maria-options from mysqld.
Thu 2011-06-09 13:35:01 +0300
- Fixed compile failure when we don't use system zlib
- Fixed crash when setting query_cache_type to 0.
Thu 2011-06-09 11:13:03 +0300
- Fixed build failure on OpenSolaris
Tue 2011-06-07 14:19:49 +0300
- Upgraded to latest handlersocket code. This fixed "Assertion `next_insert_id == 0' failed with handlersocket"
Tue 2011-06-07 10:54:37 +0300
- Fixed that mysqld --no-defaults --help --verbose doesn't give a lot of irrelevant error messages.
Tue 2011-06-07 10:29:08 +0300
- Fixed strict alias problem by replacing = with memcpy()
Mon 2011-06-06 15:50:46 -0700
- Fixed . The code that added semi-join transformations missed checking the state of the fixed flag for the items built with the and_items function before calls of the fix_fields method. This could lead to an abort failure when the first argument of and_items() happened to be NULL.
[merge] Mon 2011-06-06 19:37:33 +0300
- Merge with 5.2 to get bug fixes for thr_lock
Mon 2011-06-06 17:25:01 +0300
- Fixed that SHOW COLUMNS for a virtual persistent column shows 'PERSISTENT' instead of 'VIRTUAL' Strict mode now gives error if one tries to update a virtual column.
Fri 2011-06-03 21:45:24 +0400
- Buildbot fixes:
  - make sp.test work both with and without query_cache (attempt 2)
  - fix compile warning in make_sort_key(), as directed by SergeiG
Fri 2011-06-03 15:06:13 +0200
- Fixed compiler warning in central header file mysql_priv.h.
Fri 2011-06-03 13:42:02 +0400
- More changes from optimizer_use_mrr to optimizer_switch
Fri 2011-06-03 11:32:21 +0400
- Buildbot fixes: don't use @@optimizer_use_mrr, it has been moved into @@optimizer_switch
Fri 2011-06-03 10:49:50 +0400
- Buildbot fixes: let mysql-test/t/sp.test set @@query_cache_size only if the server has query cache.
[merge] Fri 2011-06-03 09:38:59 +0400
- Merge
- Fri 2011-06-03 00:25:58 +0400
  - Change optimizer_use_mrr=auto|disable|force to be optimizer_switch flags mrr=on|off and mrr_cost_based=on|off.
[merge] Thu 2011-06-02 17:33:08 -0700
- Merge
- Tue 2011-05-31 09:39:35 -0700
  - Corrected the previous patch concerning elimination of SQL_SELECT::original_cond.
[merge] Thu 2011-06-02 23:52:36 +0400
- Merge fix for .
- Thu 2011-06-02 23:48:33 +0400
  - : Valgrind complains on a join query with two IN subqueries
Thu 2011-06-02 16:46:47 +0400
- Change suite/rpl/t/rpl_row_basic_11bugs.test to require query cache.
[merge] Tue 2011-05-31 12:16:02 +0200
- automerge
- Tue 2011-05-31 12:14:21 +0200
  - Attempt to fix rpl.rpl_corruption failure seen in Buildbot on Windows.
Mon 2011-05-30 11:19:40 +0400
- Remove compiler warning
- Remove garbage comments
[merge] Mon 2011-05-30 10:51:41 +0400
- Merge 5.3-main ->
Sun 2011-05-29 20:48:14 -0700
- Eliminated the member original_cond from the class SQL_SELECT introduced at the latest merge 5.1->5.2->5.3. It is basically not needed since if SQL_SELECT::pre_idx_push_select_cond is not NULL then SQL_SELECT::original_cond would point to the same condition as SQL_SELECT::pre_idx_push_select_cond. Otherwise SQL_SELECT::original_cond would be equal to SQL_SELECT::cond.
Sat 2011-05-28 22:07:56 -0700
- Fixed the abort failure of a test case from vcol.vcol_misc. The fix blocks execution of any constant sub-expressions of the defining expressions for virtual columns when context analysis if these expressions is performed.
- Fixed a compiler warning.
Sat 2011-05-28 19:28:39 +0200
- Fix gcc warning.
Sat 2011-05-28 16:57:58 +0200
- Fix compile errors and warnings and test errors introduced by microseconds push.
- Also, change windows timespec definition to be Unix-ish - simplifies handling a lot.
[merge] Sat 2011-05-28 06:00:22 +0300
- Automatic merge
- [merge] Sat 2011-05-28 05:58:16 +0300
  - automatic merge with 5.3
[
- merge] Fri 2011-05-27 19:05:35 +0200
- merge
[merge] Mon 2011-05-23 11:54:26 +0300
- automatic merge with 5.3
- Mon 2011-05-23 10:56:05 +0300
  - : Address review feedback (by Sergey Petrunia)
Sat 2011-05-21 22:23:14 +0200
- Fix comp_errr crash ( fprintf crashes wheb uninitialized string is passed)
Sat 2011-05-21 00:46:18 +0300
- Changed MariaDB error numbers to start from 1900 to not conflict with MySQL error numbers
Fri 2011-05-20 19:52:24 +0400
- Fix a comment (unmatched '{' and '}' screw up jumping in advanced editors)
Fri 2011-05-20 19:08:55 +0400
- Stabilize a testcase after fix for , part 2
Fri 2011-05-20 14:15:22 +0400
- Stabilize a testcase after fix for
[merge] Fri 2011-05-20 10:13:02 +0400
- Merge fix for
- Fri 2011-05-20 01:05:06 +0400
  - : Wrong result with semijoin + nested subqueries in maria-5.3

Changelog — page: 2

MariaDB 5.3.0 Changelog p5

Download |Release Notes |Changelog (page:1 2 3 4 5 6 ) |Overview of 5.3

Release date: 26 July 2011

Revision #2880 Sat 2011-01-15 23:39:51 -0800
- Corrected test case for Bug #698882 to make it platform independent
[merge] Sat 2011-01-15 12:42:32 -0800
- Merge
- Sat 2011-01-15 11:14:36 -0800
  - Fixed .
[merge] Fri 2011-01-14 23:53:27 -0800
- Merge
- Fri 2011-01-14 22:55:56 -0800
  - Ported the fix for / .
[merge] Fri 2011-01-14 13:07:50 +0300
- Merge backported subquery bugfixes/testcases into
- Fri 2011-01-14 00:47:03 +0300
  - Backport testcase for: - Server crash with a simple multi-table update
Backport the testcase (the fix itself was included with the subquery optimizations backport)
Wed 2011-01-12 15:00:10 +0300
- : Result differences on query re-execution
  - Cause: handler::in_range_check_pushed_down was not reset when a command would call handler->idx_cond_push() without later calling handler->index_end().
  - Fix: reset the variable in handler->reset(), too (like we do with other Index Condition Pushdown members).
Wed 2011-01-05 15:03:30 -0800
- Fixed . When stored in a key buffer any varchar field has a length prefix that always takes 2 bytes.
Wed 2010-12-29 18:14:03 -0800
- Corrected the test case for Added a test case for - a duplicate of
[merge] Wed 2010-12-29 13:45:38 -0800
- Merge.
- Wed 2010-12-29 11:00:22 -0800
  - Fixed The bug was the result of a bad merge maria-5.2-wl21 -> 5.3.
Sun 2010-12-26 16:31:03 -0800
- Fixed One of the hash functions employed by the BNLH join algorithm calculates the value of hash index for key value utilizing every byte of the key buffer. To make this calculation valid one has to ensure that for any key value unused bytes of the buffer are filled with a certain filler. We choose 0 as a filler for these bytes.
- Added an optional boolean parameter with_zerofill to the function key_copy. If the value of the parameter is TRUE all unused bytes of the key buffer is filled with 0.
[merge] Sat 2010-12-25 18:54:14 -0800
- Merge
- Fri 2010-12-24 14:36:35 -0800
  - Fixed
[merge] Fri 2010-12-24 16:24:20 -0800
- Merge
- Wed 2010-12-22 00:37:35 -0800
  - Fixed Lifted the limitation that hash join could not be used over varchar fields with non-binary collation.
Wed 2010-12-22 02:26:35 +0300
- Fix compile error on Windows: instead of round(X) use floor(X+0.5)
[merge] Tue 2010-12-21 14:40:23 +0300
- -125 DS-MRR improvements
  - Merge with 5.3-main
- Mon 2010-12-20 14:40:12 +0300
Tue 2010-12-14 14:08:05 +0200
- Fix
  - Analysis:
    The assert failed because st_select_lex::print() was called for subqueries as follows:
Sat 2010-12-11 12:50:39 -0800
- Fixed compiler warnings.
[merge] Fri 2010-12-10 23:23:34 -0800
- Merge.
- Fri 2010-11-19 11:03:03 -0800
  - Got the declarations related to the class JOIN_CACHE, its derivatives and companions out of sql_select.h into a separate file sql_join_cache.h.
Wed 2010-12-08 16:16:32 +0200
- Fixed test results for windows builds
- Fixed compiler warning
[merge] Tue 2010-12-07 00:15:27 +0100
- merge
Mon 2010-12-06 20:44:17 +0300
- Post-merge fixes: fix compile failure in buildbot
[
- merge] Mon 2010-12-06 13:40:52 +0100
- merge
[merge] Mon 2010-12-06 10:25:44 +0200
- Merge with 5.1-release.
  - Fixed problem with oqgraph and 'make dist'
  - Note that after this merge we have a problem show in join_outer where we examine too many rows in one specific case (related to ).
Tue 2010-11-30 01:27:14 +0200
- Fixed some compiler warnings found when compiling for windows.
- Changed rows_read and rows_sent status variables to be longlong (to avoid compiler warnings)
Mon 2010-11-29 23:58:18 +0100
- Use three digits after the decimal point for better resolution and comparability of results.
Mon 2010-11-29 22:02:33 +0200
- Fix logical expression according to operation priority (also MS visual studio compiler warnings).
[merge] Mon 2010-11-29 13:50:56 +0200
- Auto-merge fix for
- Thu 2010-11-25 11:43:23 +0200
  - Fix
Sun 2010-11-28 15:02:12 +0200
- Disable warning that comes 'occasionable' depending on if HAVING is executed or not.
[merge] Sun 2010-11-28 14:38:59 +0200
- Automatic merge
- Sat 2010-11-27 17:29:52 +0200
  - Added TRASH() to table->record[0] to find out if we access not initialzed data.
Thu 2010-11-25 00:34:50 +0200
- Fix
- Analysis:
  - The send_data method of the result sink class used to collect data statistics about materialized subqueries incorrectly assumed that duplicate rows are removed prior to calling send_data. As a result the collected statistics was wrong, which resulted in an incorrect maximal number of keys in the Ordered_key buffer.
Tue 2010-11-23 12:35:37 +0200
- Fix for : Adding bit field support for heap tables.
[merge] Thu 2010-11-11 14:35:26 +0200
- Merge in
- Tue 2010-11-02 21:13:53 +0300
  - : RQG: sql_select.cc:5385: bool greedy_search... : Assertion `join->best_read
[merge] Tue 2010-11-09 19:40:02 -0800
- Merge
- Mon 2010-11-08 20:36:32 -0800
  - Fixed .
Tue 2010-11-09 13:13:56 +0200
- Fixed Incorrect processing of NULL result in Item_cache fixed.
Tue 2010-11-09 09:52:22 +0200
- Fix buildbot failure introduced by the previous push
Mon 2010-11-08 23:25:12 +0200
- Fix buildbot failures caused by two previous pushes.
Mon 2010-11-08 20:51:31 +0300
- Fix buildbot errors: rec_per_key_part can be 0 if re-opening
Mon 2010-11-08 19:06:26 +0300
- [Patch from Monty] Fix stack-overrun crash in subselect_notembedded.test
  - Make mi_open() use less stack space
[merge] Fri 2010-11-05 12:37:51 +0200
- Automerge with 5.2
Fri 2010-11-05 11:54:42 +0200
- Fixed usage of wrong variable in case of errors
[merge] Tue 2010-11-02 16:08:02 -0700
- Merge
- [merge] Tue 2010-11-02 10:12:21 -0700
  - Merge
Tue 2010-11-02 16:04:39 -0700
- Removed empty lines.
[merge] Tue 2010-11-02 10:48:55 +0100
- merge
- Tue 2010-11-02 10:47:36 +0100
  - fix windows embedded
Tue 2010-11-02 11:03:33 +0200
- Fixed wrong queue_replace(), which caused timeout failure in pbxt.flush_read_lock_kill
- Fixed compiler warnings.
Fri 2010-10-29 18:59:39 -0700
- Fixed .
- The bug could cause wrong results for queries over Maria tables when index condition pushdown was used.
[merge] Thu 2010-10-28 19:04:23 +0200
- 5.2 merge
Wed 2010-10-27 16:28:19 +0300
- Fixed
- The set of Ordered keys of a rowid merge engine is dense. Thus when we decide not to create a key for a column that has only NULLs, this column shouldn't be counted.
- Notice that the caller has already precomputed the correct total number of keys that should be created.
Wed 2010-10-27 12:35:15 +0300
- Fixed
- Post-review fix - avoid re-evaluation of the having clause when it evaluates to true.
Wed 2010-10-27 06:03:59 +0300
- Type of the variables fixed.
Tue 2010-10-26 14:55:42 +0300
- Fixed
- The cause for this bug is that still processes derived tables (subqueries in the FROM clause) by fully executing them during the parse phase. This will be remedied by once merged into the main 5.3.
- The assert statement is triggered when MATERIALIZATION is ON for EXPLAIN EXTENDED for derived tables with an IN subquery as follows:

Changelog — page: 5

MariaDB 5.3.4 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 15 Feb 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3421 Tue 2012-02-14 16:52:56 +0200
- Fix for causes 1093 error on Drupal
- Problem was that now we can merge derived table (subquery in the FROM clause).
- Fix: in case of detected conflict and presence of derived table "over" the table which cased the conflict - try materialization strategy.
Tue 2012-02-14 16:04:06 +0400
- Review and push crashsafe GIS keys.
- tests for RTree keys recovery.
[merge] Tue 2012-02-14 14:13:10 +0400
- Merge fix for
- Tue 2012-02-14 13:58:57 +0400
  - : Query containing IN subquery with OR in the where clause returns a wrong result
Mon 2012-02-13 23:46:57 -0800
- Fixed .
- If the flag 'optimize_join_buffer_size' is set to 'off' and the value of the system variable 'join_buffer_size' is greater than the value of the system variable 'join_buffer_space_limit' than no join cache can be employed to join tables of the executed query.
- A bug in the function JOIN_CACHE::alloc_buffer allowed to use join buffer even in this case while another bug in the function revise_cache_usage could cause a crash of the server in this case if the chosen execution plan for the query contained outer join or semi-join operation.
Mon 2012-02-13 17:14:10 +0100
- When we fail during slave thread initialisation, keep mi->run_lock locked until we have finished clean up.
- Previously, the code released the lock without marking that the thread was running. This allowed a new slave thread to start while the old one was still in the middle of cleaning up, causing assertions and probably general mayhem.
[merge] Sun 2012-02-12 23:03:36 +0100
- merge
- Sun 2012-02-12 23:02:56 +0100
  - Use newly released HeidiSQL 7.0 in the MSI installer
[merge] Sat 2012-02-11 15:00:15 +0100
- merge
- [merge] Sat 2012-02-11 14:57:44 +0100
  - Fix for , - broken SSL connectivity for some connectors
[merge] Fri 2012-02-10 22:09:57 +0100
- Merge fix for : Race condition in kill_threads_for_user().
- [merge] Fri 2012-02-10 21:20:32 +0100
  - Merge fix for : Race condition in kill_threads_for_user().
[merge] Fri 2012-02-10 22:56:34 +0200
- Automatic merge
- Fri 2012-02-10 22:53:46 +0200
  - Fixed that prepared statements are properly igored (if possible) by query cache.
Thu 2012-02-09 23:35:26 +0200
- Test case for
- The bug itself is fixed by the patch for
Fri 2012-02-03 12:49:17 -0800
- Made mrr related counters temporarily invisible until we agree upon their names.
Fri 2012-02-03 16:56:12 +0200
- Fixed typos in Query Cache.
[merge] Fri 2012-02-03 13:32:29 +0200
- Merge with 5.2
- Fri 2012-02-03 12:24:55 +0200
  - Fixed DELETE issues of view over view over table.
Fri 2012-02-03 13:01:05 +0200
- Moving to 5.3 + fixing INSERT of multi-table view.
Fri 2012-02-03 00:46:34 -0800
- Back-ported the fix for bug #12831587 from mysql-5.6 code line.
- The comment for the fix commit says:
  - Due to the changes required by ICP we first copy a row from the InnoDB format to the MySQL row buffer and then copy it to the pre-fetch queue. This was done for the non-ICP code path too. This change removes the double copy for the latter.
Thu 2012-02-02 22:22:27 -0800
- Applied the patch from mysql-5.6 code line that fixed a significant performance drop for high concurrency bechmarks (bug #11765850
).
Here's the comment of the patch commit:
- The bug is that the InnoDB pre-fetch cache was not being used in row_search_for_mysql(). Secondly the changeset that planted the bug also introduced some inefficient code. It would read an extra row, convert it to MySQL row format (for ICP==off), copy the row to the pre-fetch cache row buffer, then check for cache overflow and dequeue the row that was pushed if there was a possibility of a cache overflow.
[merge] Wed 2012-02-01 17:48:45 -0800
- Merge.
- [merge] Wed 2012-02-01 15:48:02 -0800
  - Merge 5.2->5.3 in preparation for the release of mariadb-5.3.4-rc.
Wed 2012-02-01 17:09:49 +0200
- fix for
- Problem was in try to check/use Item_direct_ref of derived view when we have to use real Item_field under it.
Tue 2012-01-31 21:12:26 +0100
- sort status variables alphabetically in mysqld.cc
Mon 2012-01-30 20:34:47 +0400
- : Loosescan reports different result than other semijoin methods
- If LooseScan is used with quick select, require that quick select produces data in key order (this disables use of MRR, which can return data in arbitrary order).
[merge] Mon 2012-01-30 17:38:14 +0400
- Merge fix for
  - Fri 2012-01-27 17:35:26 +0400
    : Assertion `0' failed at item_cmpfunc.cc:5899: Item* Item_equal::get_first(JOIN_TAB*, Item*)
Sat 2012-01-28 01:12:45 -0800
- Fixed
- Applied the fix for bug #12546542 from the mysql-5.6 code line:
- JOIN_CACHE::join_records forgot to reset JOIN_TAB::first_unmatched in some cases.
[merge] Fri 2012-01-27 19:23:08 -0800
- Merge.
- Fri 2012-01-27 19:01:26 -0800
  - Back-ported test cases for of mysql-5.6 code line. The bug could not be reproduced in the latest release of mariadb-5.3 as it was fixed by Sergey Petrunia when working on the problems concerning outer joins within in subqueries converted to semi-joins.
Fri 2012-01-27 17:51:40 +0400
- Make testcase stable by adding --sorted_result for SHOW STATUS commands.
Thu 2012-01-26 14:20:34 +0400
- Fix compile failure when built without query cache: define QUERY_CACHE_DB_LENGTH_SIZE 0, just like it is done with QUERY_CACHE_FLAGS_SIZE.
Thu 2012-01-26 12:22:02 +0400
- Sort counters by name (will this make them show in the same order on all platforms?)
Wed 2012-01-25 22:05:20 +0400
- : Wrong result (missing rows) with firstmatch+BNL, IN subquery, ...
  - Disable use of join cache when we're using FirstMatch strategy, and the join order is such that subquery's inner tables are interleaved with outer. Join buffering code is incapable of handling such join orders.
  - The testcase requires use of @@debug_optimizer_prefer_join_prefix to hit the bug, but I'm pushing it anyway (including the mention of the variable in .test file), so that it can be found and enabled when/if we get something comparable in the main tree.
[merge] Wed 2012-01-25 18:36:57 +0400
- Merge
- Wed 2012-01-25 18:33:57 +0400
  - : Wrong result (extra rows) with loosescan and IN subquery
Mon 2012-01-23 15:14:13 +0200
- Fixed creating limit for exists subquery.
Sun 2012-01-22 12:54:30 -0800
- Back-ported test cases for , , , from subquery_sj of mysql-5.6 code line. The bugs could not be reproduced in the latest release of mariadb-5.3 as they were fixed either when the code of subquery optimization was back-ported from mysql-6.0 or later when some other bugs were fixed.
Sat 2012-01-21 20:58:23 -0800
- Back-ported test cases for , , , from subquery_sj of mysql-5.6 code line. The bugs could not be reproduced in the latest release of mariadb-5.3 as they were fixed either when the code of subquery optimization was back-ported from mysql-6.0 or later when some other bugs were fixed.
Fri 2012-01-20 02:11:53 +0400
- : Wrong result (missing rows) with join_cache_hashed+materialization+semijoin=on
- equality substitution code was geared towards processing WHERE/ON clauses. that is, it assumed that it was doing substitions on the code that
  - wasn't attached to any particular join_tab yet
Thu 2012-01-19 23:44:43 +0400
- : Wrong result (missing rows) with semijoin=on, firstmatch=on, ...
  - setup_semijoin_dups_elimination() would incorrectly set join_tab->do_firstmatch when the join order had outer tables interleaved with inner.
Thu 2012-01-19 13:46:59 +0100
- Fix compiler warning on Windows.
[merge] Wed 2012-01-18 15:28:13 -0800
- Merge
  - [merge] Wed 2012-01-18 14:19:28 -0800
    Merge
Wed 2012-01-18 14:52:56 +0100
- multi-delete should ignore semi-join internal temp tables, when looking for tables to delete from
[merge] Wed 2012-01-18 14:52:38 +0100
- more problems found by PVS Studio
- [merge] Mon 2011-11-14 00:21:22 +0100
  - 5.2->5.3 merge
Wed 2012-01-18 12:53:50 +0200
- Adjust test results after Monty's push of the new handler counter Handler_read_rnd_deleted.
Tue 2012-01-17 15:16:00 +0200
- Removed unused code merged from 5.2. In 5.3 we fix this problem by checking if we put max/min group function without GROUP BY artificially in case of MODE_ONLY_FULL_GROUP_BY sql mode.
Fri 2012-01-13 14:35:49 +0200
- Added Handler_read_rnd_deleted, number of deleted rows found with ha_read_rnd_first.
Wed 2012-01-11 10:35:16 +0200
- Fix the comment.
Tue 2012-01-10 23:26:00 +0200
- Fix for Wrong result with subquery in select list, EXISTS, constant MyISAM/Aria table.
- Problem: When building the condition for JOIN::outer_ref_cond the optimizer forgot to take into account that this condition could depend on constant tables as well.
[merge] Tue 2012-01-10 18:20:56 +0400
- Merge fix for
- Sun 2012-01-08 14:43:14 +0400
  - : Crash in do_copy_not_null with semijoin=ON, firstmatch=ON, aggregate ...
Mon 2012-01-09 13:49:47 +0200
- Fixed that --sorted-result in mysql-test-run also works for exec
Sun 2012-01-08 21:14:07 +0100
- - possible deadlock in XtraDB async io subsystem on Windows.
- Split IO threads into ones that handle only read completion and ones that handle only write completion, as it was originally done, but got lost with "completion port" patch. The reason we need to have dedicated read and dedicated write threads is that read completion routine can block waiting for write io to complete, and in rare cases where all io threads are handling async reads, it can deadlock.
Mon 2012-01-02 20:06:36 -0800
- Fixed
- The patch for erroneously removed a call of engine->set_thd() from Item_subselect::fix_fields().
Fri 2011-12-30 22:19:05 +0100
- Make test results stable.
Fri 2011-12-30 20:22:52 +0100
- Update version in configure.in (was forgotten in 5.3.3 release).
Fri 2011-12-30 11:34:29 +0100
- Continuation of the efforts in previous cset.
Thu 2011-12-29 22:29:02 +0100
- Make test results stable (they weren't, because filesort() used to read from a heap temptable, which uses pointers to records (that is, byte* pointers) as rowids.
- This meant that for rows with the same sort key value, the order was determined by memory layout.
Wed 2011-12-28 12:12:48 +0400
- Update test results.
[merge] Wed 2011-12-28 03:37:34 +0400
- Merge
- Tue 2011-12-20 00:55:32 +0400
  - : Incorrect result with outer join and full text match
Sun 2011-12-25 18:03:03 -0800
- Changed a test case from join_cache.test to make it platform independent.
Sat 2011-12-24 08:55:10 -0800
- Back-ported the patch of the mysql-5.6 code line that fixed several defects in the greedy optimization:
  1. The greedy optimizer calculated the 'compare-cost' (CPU-cost) for iterating over the partial plan result at each level in the query plan as 'record_count / (double) TIME_FOR_COMPARE'

This cost was only used locally for 'best' calculation at each level, and not accumulated into the total cost for the query plan.

This fix added the 'CPU-cost' of processing 'current_record_count' records at each level to 'current_read_time' before it is used as 'accumulated cost' argument to recursive best_extension_by_limited_search() calls. This ensured that the cost of a huge join-fanout early in the QEP was correctly reflected in the cost of the final QEP.

To get identical cost for a 'best' optimized query and a straight_join with the same join order, the same change was also applied to optimize_straight_join() and get_partial_join_cost() 1. Furthermore to get equal cost for 'best' optimized query and a straight_join the new code substrcated the same '0.001' in optimize_straight_join() as it had been already done in best_extension_by_limited_search() 1. When best_extension_by_limited_search() aggregated the 'best' plan a plan was 'best' by the check :

'if ((search_depth == 1) || (current_read_time < join->best_read))'

The term '(search_depth == 1' incorrectly caused a new best plan to be collected whenever the specified 'search_depth' was reached - even if this partial query plan was more expensive than what we had already found.

MariaDB 5.3.0 Changelog p4

Download |Release Notes |Changelog (page:1 2 3 4 5 6 ) |Overview of 5.3

Release date: 26 July 2011

Revision #2945 [merge] Tue 2011-03-15 12:30:48 -0700
- Merge.
- Thu 2011-03-03 18:24:41 -0800
  - Fixed : The bug was a result of the fix for that turned out to be not quite correct. A problem appeared with HAVING conditions containing more than one predicate. If a query with an ORDER BY clause uses such HAVING condition and the required order can be obtained with a range/index scan then the HAVING condition has to be pushed into two different formulas (items). To be able to do it we have to create a copy of the ANDOR structure of the pushed condition.
[merge] Sun 2011-03-13 16:57:05 +0000
- Merge in the fix for , and a corrected fix for , after Monty's review.
- Sun 2011-03-13 15:03:26 +0000
  - Fix ,
[merge] Sun 2011-03-13 03:50:14 -0700
- Merge
- Mon 2011-03-07 22:09:21 -0800
  - Fixed : If join condition is of the form <t2.key>=<t1.no_key> then the server performs no index look-ups when looking for matching rows of t2 for the rows from t1 with t1.no_key=NULL. It happens because the function add_not_null_conds() injects an additional condition of the form IS NOT NULL(<t1.no_key>) into the WHERE condition. However if the join condition was of the form <t.key>=<outer_ref> no additional null rejecting predicate was generated. This could lead to extra records in the result set if the value of <outer_ref> happened to be NULL.
Sat 2011-03-12 16:18:02 +0000
- Fix wrong use of compiler flag causing the build to fail in handlersocket.
[merge] Sat 2011-03-12 05:14:10 -0800
- Merge.
- Sat 2011-03-12 00:49:03 -0800
  - Fixed LP bugs / : Do not reset the value of the item_equal field in the Item_field object once it has been set.
[
- merge] Fri 2011-03-11 16:08:26 +0100
- merge
[
- merge] Fri 2011-03-11 15:47:15 +0100
- merge
[merge] Fri 2011-03-11 15:20:24 +0100
- merge
Wed 2011-03-09 17:55:00 +0200
- Added item.real_type() for easy access to the underlaying types for Item_ref and Item_cache_wrapper() This allows us to simplify and speed up some tests and also remove get_cached_item()
[merge] Wed 2011-03-09 15:47:59 +0200
- Merge with 5.2
Wed 2011-03-09 00:51:22 +0200
- Added define to get rid of compiler warnings on system without DLOPEN
Tue 2011-03-08 23:23:44 +0200
- Fix
  - Analysis:
    The assert failed because the execution code for partial matching is designed with the assumption that NULLs on the left side are detected as early as possible, and a NULL result is returned before any lookups are performed at all.
[merge] Fri 2011-03-04 18:54:30 +0300
- Merge in MRR interface fixes.
- Fri 2011-03-04 12:06:03 +0300
  - MRR interface: change range_info's type from char* to range_id_t typedef. The goals are:
Fri 2011-03-04 12:14:46 +0300
- Make testcase pass on systems with lower_case_table_names=2.
  - Generally, we should use only small letters for table names but here it's easier to fix with one --replace.
[merge] Fri 2011-03-04 01:30:25 +0300
- Merge fix for
- Wed 2011-03-02 23:08:13 +0300
  - : Assertion multi_range_read.cc:908: int DsMrr_impl::dsmrr_init
[merge] Fri 2011-03-04 01:28:02 +0300
- Merge .
- Fri 2011-03-04 00:54:10 +0300
  - : Wrong result with join_cache_level=6 optimizer_use_mrr = force (incremental, BKA join)
Thu 2011-03-03 23:48:31 +0200
- Fix
  - Analysis:
    The reason for the crash was that the inner subquery was executed via a scan on a final temporary table applied after all other operations. This final operation is implemented by changing the contents of the JOIN object of the subquery to represent a table scan over the temp table. At the same time query optimization of the outer subquery required evaluation of the inner subquery, which happened before the actual EXPLAIN. The evaluation left the JOIN object of the inner subquery in the changed state, where it represented a table scan over a temp table, and EXPLAIN crashed because the temp table is not associated with any table reference (TABLE_LIST object). The reason the JOIN was not restored was because its saving/restoration was controlled by the join->select_lex->uncacheable flag, which was not set in the case of materialization.
[merge] Tue 2011-03-01 10:22:22 +0300
- Merge fix for
- Tue 2011-03-01 00:29:59 +0300
  - : Crash in JOIN::optimize in maria-5.3
Mon 2011-02-28 17:27:41 -0800
- Moved the test case for into a new test file.
Sun 2011-02-27 22:37:46 -0800
- Fixed : The bug in the function print_keyuse() caused crashes if hash join could be used. It happened because the function ignored the fact that KEYUSE structures could be created for hash joins as well.
[merge] Sun 2011-02-27 10:14:11 -0800
- Merge.
- Sun 2011-02-27 09:35:14 -0800
  - Minor corrections.
[merge] Sun 2011-02-27 00:21:45 -0800
- Merge
- Thu 2011-02-24 10:36:32 -0800
  - Made a newly added EXPLAIN platform independent.
Sat 2011-02-26 23:09:58 +0300
- Fix buildbot failure in fix of
[merge] Fri 2011-02-25 21:45:21 +0300
- Merge of fix for
- Fri 2011-02-25 21:43:57 +0300
  - : Crash in get_constant_key_infix with EXISTS ( SELECT .. DISTINCT )
[merge] Fri 2011-02-25 20:32:18 +0200
- automatic merge
- Fri 2011-02-25 20:15:27 +0200
  - Fixed compiler warnings
Thu 2011-02-24 23:32:00 +0300
- : innodb_mysql.test fails with --embedded-server
  - Don't access THD::killed directly from ha_innodb.cc. This is forbidden because THD has different membership (and so, different member offsets) in regular and embedded server. Access must be done through thd_killed() function.
Wed 2011-02-23 14:46:16 +0200
- Fixed build issues
  - Linking now with g++ instead of gcc with 'compile-dist' to solve problems with handlersocket/client
  - Fixed bug in heap tables when doing handler read next-prev over last row
Wed 2011-02-23 02:06:58 +0200
- Fixed compiler warnings and some test failures found by buildbot
[merge] Tue 2011-02-22 11:30:51 +0200
- Merge with main
- [merge] Tue 2011-02-22 11:15:47 +0200
  - Merge in new handler and handlersocket code into 5.3 main
Mon 2011-02-21 20:17:26 +0100
- :Fixed dependency to prevent occasional situations where bison runs in parallel with the same input and output files
Mon 2011-02-21 14:23:44 +0100
- Fix remaining 5.2 buildbot problems:
  - Cherrypick (PBXT crashes in debug/x64)
  - Fix unixism (rm -rf) in the test suite_timeout
Sat 2011-02-19 15:21:50 +0100
- add newline at the end of file
Sat 2011-02-19 15:16:31 +0100
- Fix remaining windows (32 bit) warnings.
Sat 2011-02-19 13:43:01 +0100
- Fixed high-impact Windows 64bit warnings (at least 4000 of them)
Sat 2011-02-19 02:42:08 +0100
- Fixed DBUG_PRINT formatting (compile error on Linux with -Werror)
Fri 2011-02-18 23:31:01 +0100
- Fix numerous warnings introduced in the last pushes on Windows
Fri 2011-02-18 22:38:22 +0100
- Linker error, missing extern "C" for mi_killed.
- Fix is to move extern "C" at the start of header file.
[merge] Fri 2011-02-18 21:45:32 +0200
- Merge with bugfix
- Fri 2011-02-18 17:43:59 +0200
  - Fix for "Index Condition Pushdown can make a thread hold MyISAM locks as well as be unKILLable for long time"
Sat 2011-02-12 18:43:22 +0100
- Workaround CMake bug Huge static libraries like libmysqld might not build if /MACHINE flag is missing for librarian with the correct processor architecture.
- Fix is to add /MACHINE flag for x64 builds
Sat 2011-02-12 17:44:01 +0100
- Fix test suite - adjust result files
Sat 2011-02-12 17:17:19 +0100
- Fix : sel_arg_range_seq_next loops in optimized compilation/VS2010
  - When is compiler with VS2010, several tests would enter infinite loop in sel_arg_range_seq_next(). The reason is compiler backend bug. This bug is not present in either VS2008 or VS2010 SP1 RC.
  - Workaround is to compile this function without most aggresive optimization flag (-Og ) using #pragma optimize ("g", {on|off}) for this version of MSVC compiler.
Sat 2011-02-12 15:43:24 +0100
- Fix Aria engine build
  - add forgotten source file
[merge] Fri 2011-02-11 13:27:35 +0300
- Merge: : "Range checked for each record" is not used if condition refers to outside of subquery
- Thu 2011-02-10 11:36:43 +0300
  - : "Range checked for each record" is not used if condition refers to outside of subquery
[merge] Wed 2011-02-09 11:22:26 -0800
- Merge
- Fri 2011-02-04 19:06:35 -0800
  - Introduced optimizer switch flag 'optimize_join_buffer_size'.
Tue 2011-02-08 19:17:12 -0800
- Backported test case for .
[merge] Mon 2011-02-07 15:19:03 -0800
- Merge
- Sat 2011-02-05 20:57:03 -0800
  - Fixed that caused a crash on the tree for with the test case added by this patch.
Tue 2011-02-01 14:19:58 +0100
- Fix compile errors:
  - declaration in the middle of the block in C file.
  - round() is only available in C99.
Mon 2011-01-31 19:33:32 -0800
- Back-ported the patch for from mysql-5.6 code line.
- The patch fixed the following optimizer defect: when performing substitution for best equal fields into where conditions to be able to do their evaluations as soon as possible the optimizer skipped conditions over views. That could lead to suboptimal execution of queries that used views.
- Slightly changed the test case to demonstrate the performance improvements if this fix.
[merge] Fri 2011-01-28 18:54:30 -0800
- Merge
- Mon 2011-01-24 14:54:50 -0800
  - Post-second-review fixes for the patch that added the code allowing to use hash join over equi-join conditions without supporting indexes.
Thu 2011-01-27 21:23:02 -0800
- Fixed .
  - This bug could manifest itself when hash join over a varchar column with NULL values in some rows was used. It happened because the function key_buf_cmp erroneously returned FALSE when one of the joined key fields was null while the second was not.
  - Also fixed two other bugs in the functions key_hashnr and key_buf_cmp that could possibly lead to wrong results for some queries that used hash join over several columns with nulls.
Wed 2011-01-26 20:45:23 -0800
- Fixed .
  - This was another bug in the patch for . The new code from this patch did not ensured that substitutions of fields for best equal fields were performed on all AND-OR levels. As a result substitutions for best fields in some predicates that had been used by the range optimizer were not actually performed while range plans could employ these substitutions. This could lead to inconsistent data structures and ultimately to a crash.
Wed 2011-01-26 11:30:29 -0800
- Fixed .
  - The bug was in the code of the patch fixing .
  - With improper casting the method store_key_field::change_source_field was called for the elements of the array TABLE_REF::key_copy that were either of a different type or not allocated at all. This caused crashes in some queries.
Sat 2011-01-22 23:45:52 -0800
- Fixed typo that caused printing 'range' instead of 'index_merge' as the type of sort_intersect scans.
Fri 2011-01-21 09:56:55 +0200
- Fix of reverting changes in depend_on list.
Fri 2011-01-14 21:51:55 +0100
- issue an informative error message for a common Aria problem when opening a table (incorrect block size)
Fri 2011-01-14 21:02:51 +0100
- compilation failures caused by adding new row format to Aria
Fri 2011-01-14 12:05:46 +0100
- Optimize use of SEARCH_SAVE_BUFF in Aria (less not-needed copies of key pages)
Fri 2011-01-14 12:03:41 +0100
- use bulk insert and repair by sort for unique keys in Aria and MyISAM in create_internal_tmp_table_from_heap()
  - (safe, as duplicates are impossible).
  - This gives a HUGE speed boost!
Fri 2011-01-14 11:58:45 +0100
- Added ha_write_tmp_row() for slightly faster write_row for internal temp tables.
- This will also enable us in the future to collect statistics for writes to internal tmp tables.
Fri 2011-01-14 11:54:39 +0100
- Added support for NO_RECORD record format (don't store any row data) for Aria.
- This makes the keys smaller (no row pointer) and gives us proper errors if we use the table wrongly.
Fri 2011-01-14 11:43:42 +0100
- use normal unique (HA_NOSAME) keys for expression cache temptables, not "uniques", that are hash-based keys.
Fri 2011-01-14 11:37:23 +0100
- Added to Aria better hash for packed numeric data for unique handling.
- This was needed as the old code caused us to have LOTS of duplicate hash values when used by optimizer.
Fri 2011-01-14 11:34:41 +0100
- compare "Copying to tmp table" proc_info as a pointer, not as a string
Fri 2011-01-14 11:31:09 +0100
- Removed some old comments.
[merge] Tue 2011-01-18 00:26:04 +0300
- Merge 5.3-subquery-bugfixing -> 5.3
- Mon 2011-01-17 15:09:30 +0300
  - Enable testcase for

Changelog — page: 4

MariaDB 5.3.8 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 28 Aug 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3564 Fri 2012-08-24 23:43:18 +0200
- oqgraph 5.5 crashes in buildbot
- force -fno-strict-aliasing for oqgraph
Sat 2012-08-25 09:15:57 +0300
- fix for
- The problem was that was_null and null_value variables was reset in each reexecution of IN subquery, but engine rerun only for non-constant subqueries.
- Fixed checking constant in Item_equal sort.
[merge] Fri 2012-08-24 19:13:34 +0200
- Merge from 5.2
- [merge] Fri 2012-08-24 19:12:47 +0200
  - Merge from 5.1
[merge] Fri 2012-08-24 15:39:34 +0200
- Merge from 5.2.
- [merge] Fri 2012-08-24 15:37:39 +0200
  - Merge from 5.1.
[merge] Fri 2012-08-24 14:26:23 +0200
- Merge into latest 5.3
- [merge] Fri 2012-08-24 14:02:32 +0200
  - merge from 5.2
Thu 2012-08-23 13:52:36 +0200
- remove mysql-5.1 assert that is already absent in mysql-5.5
Wed 2012-08-22 18:40:27 +0200
- mysql-test-run --valgrind main.ps_2myisam gives warning about not initialized memory
- Item::get_date() should return 1 unless the value is a valid date.
[merge] Wed 2012-08-22 16:45:25 +0200
- 5.2 merge.
- two tests still fail:
  - main.innodb_icp and main.range_vs_index_merge_innodb
Tue 2012-08-21 22:24:34 +0400
- Better comments
Tue 2012-08-14 14:25:56 -0700
- Corrected the pactch for to fix valgrind failures.
Mon 2012-08-13 21:13:14 -0700
- Fixed bug .
- The bug could caused a crash when the server executed a query with ORDER by and sort_buffer_size was set to a small enough number.
- It happened because the small sort buffer did not allow to allocate all merge buffers in it.
[merge] Thu 2012-08-02 00:58:13 +0400
- (Mismatches in MySQL engines test suite)
- Following reasons caused mismatches:
  - different handling of invalid values;
Wed 2012-07-18 15:03:05 +0400
- : Sergv related to spacial queries
- index_merge/intersection is unable to work on GIS indexes, because:
  1. index scans have no Rowid-Ordered-Retrieval property
Tue 2012-06-26 21:43:34 +0300
- Fix for
- TABLE_LIST::check_single_table made aware about fact that now if table attached to a merged view it can be (unopened) temporary table (in 5.2 it was always leaf table or non (in case of several tables)).
[merge] Sat 2012-06-23 15:00:05 -0700
- Merge 5.2->5.3
- Sat 2012-06-23 12:19:07 -0700
  - Fixed bug .
Fri 2012-06-22 14:14:22 +0400
- Added comment about QUICK_RANGE_SELECT::free_cond being unused.
Thu 2012-06-21 14:33:36 +0400
- Update test results (checked)
Wed 2012-06-20 22:30:24 +0400
- Update test results.
Wed 2012-06-20 13:41:31 +0400
- Post-merge fixes:
  - put back the result encoding in func_in.result (messed up by kdiff3)
  - update .result for other tests (checked)
[merge] Mon 2012-06-18 22:38:11 +0400
- Merge 5.2->5.3
- Tue 2012-06-12 10:06:26 -0700
  - Adjusted results in pbxt.negation_elimination after the fix for lp bug 992380.
Fri 2012-06-15 11:33:24 +0300
- Fix
- Analysis:
  - The fix for bug implements the method Item_subselect::no_rows_in_result() for all main kinds of subqueries. The purpose of this method is to be called from return_zero_rows() and set Items to some default value in the case when a query returns no rows. Aggregates and subqueries require special treatment in this case.
Thu 2012-06-14 17:03:09 +0300
- Fix
- Analysis:
  - Queries with implicit grouping (there is aggregate, but no group by) follow some non-obvious semantics in the case of empty result set. Aggregate functions produce some special "natural" value depending on the function. For instance MIN/MAX return NULL, COUNT returns 0.
[merge] Sun 2012-06-10 14:06:11 +0400
- Merge
- [merge] Sun 2012-06-10 13:53:06 +0400
  - Merge from 5.1 to 5.2
Fri 2012-06-08 19:15:01 +0200
- : Speedup specific datetime queries that got slower with introduction of microseconds in 5.3
  - Item::get_seconds() now skips decimal arithmetic, if decimals is 0. This significantly speeds up from_unixtime() if no fractional part is passed.
  - replace sprintfs used to format temporal values by hand-coded formatting
Wed 2012-06-06 23:02:21 +0300
- Fixed pbxt test case not run by default.
Tue 2012-06-05 17:25:10 +0300
- Fixed
- Analysis:
  - When the method JOIN::choose_subquery_plan() decided to apply the IN-TO-EXISTS strategy, it set the unit and select_lex uncacheable flag to UNCACHEABLE_DEPENDENT_INJECTED unconditionally.
Mon 2012-06-04 23:22:03 +0200
- - Failing assertion: templ->mysql_col_len == len
- remove the offending assert.
- take the test case from
[merge] Sat 2012-06-02 16:13:05 +0400
- Merge
- Sat 2012-06-02 03:25:56 +0400
  - : Multi-table DELETE that uses innodb + index_merge/intersect may fail to delete rows
Fri 2012-06-01 14:56:47 +0200
- : Insufficient buffer allocation for Query_log_event
- The constructor for Query_log_event allocated 2 bytes too few for extra space needed by Query cache. (Not sure if this is reproducible in practice, as there are often a couple of extra bytes allocated for unused string zero terminators, but better safe than sorry).
Wed 2012-05-30 19:10:18 +0300
- Fix for
- Analysis:
  - When a subquery that needs a temp table is executed during the prepare or optimize phase of the outer query, at the end of the subquery execution all the JOIN_TABs of the subquery are replaced by a new JOIN_TAB that selects from the temp table. However that temp table has no corresponding TABLE_LIST. Once EXPLAIN execution reaches its last phase, it tries to print the names of the subquery tables through its TABLE_LISTs, but in the case of this bug there is no such TABLE_LIST (it is NULL), hence a crash.
Tue 2012-05-29 09:59:25 +0500
- SELECT WHERE ST_CONTAINS doesn't return all the records where ST_CONTAINS() is 1.
- Optimizator fails using index with ST_Within(g, constant_poly).
- per-file comments:
[merge] Fri 2012-05-25 00:44:43 -0700
- Merge.
- Fri 2012-05-25 00:07:26 -0700
  - Fixed a performance problem: calls of the function imerge_list_and_tree could lead an to exponential growth of the imerge lists.
Fri 2012-05-25 01:20:40 +0400
- : Valgrind warnings 'Invalid read' in subselect_engine::calc_const_tables with SELECT
  - In JOIN::exec(), make the having->update_used_tables() call before we've made the JOIN::cleanup(full=true) call. The latter frees SJ-Materialization structures, which correlated subquery predicate items attempt to walk afterwards.
Wed 2012-05-23 21:05:53 +0400
- Update test results after the latest push
Wed 2012-05-23 11:55:14 +0400
- : Query with simple join and ORDER BY takes thousands times longer when run with ICP
  - Correct testcases.
Wed 2012-05-23 11:46:40 +0400
- : Query with simple join and ORDER BY takes thousands times longer when run with ICP
  - Disable IndexConditionPushdown for reverse scans.
Tue 2012-05-22 15:22:55 +0300
- Fix
- Analysis:
  - The optimizer detects an empty result through constant table optimization. Then it calls return_zero_rows(), which in turns calls inderctly Item_maxmin_subselect::no_rows_in_result(). The latter method set "value=0", however "value" is pointer to Item_cache, and not just an integer value.
Solution:
- When the optimizer discovers an empty result set, set Item_singlerow_subselect::value to a FALSE constant Item instead of NULL.
Mon 2012-05-21 19:37:46 +0500
- Non-blocking "set read_only".
- Handle the 'set read_only=1' in lighter way, than the FLUSH TABLES READ LOCK;
- For the transactional engines we don't wait for operations on that tables to finish.
[merge] Sun 2012-05-20 14:57:29 +0200
- 5.2 merge
- [merge] Fri 2012-05-18 14:23:05 +0200
  - 5.1 merge
[merge] Fri 2012-05-18 16:28:11 +0400
- Merge
- Fri 2012-05-18 16:24:12 +0400
  - : Wrong result (extra rows) with semijoin+materialization, IN subqueries, join_cache_level>0
Thu 2012-05-17 10:45:20 +0300
- Test suite of fixed bug ().
Tue 2012-05-15 08:31:07 +0300
- Fix for
- If we did nothing in resolving unique table conflict we should not retry (it leed to infinite loop).
- Now we retry (recheck) unique table check only in case if we materialized a table.
Sun 2012-05-13 13:15:17 +0400
- : Assertion failure or valgrind errors at best_access_path ...
- Let fix_semijoin_strategies_for_picked_join_order() set POSITION::prefix_record_count for POSITION records that it copies from SJ_MATERIALIZATION_INFO::tables.
- (These records do not have prefix_record_count set, because they are optimized as joins-inside-semijoin-nests, without full advance_sj_state() processing).
[merge] Sat 2012-05-12 12:27:26 +0400
- Merge 5.2->5.3
- [merge] Sat 2012-05-12 12:12:35 +0400
  - Merge 5.2->5.3
[merge] Fri 2012-05-11 11:40:23 +0300
- Merge 5.2->5.3
- Fri 2012-05-11 09:35:46 +0300
  - fix for
Mon 2012-05-07 13:26:34 +0300
- Fix for
- Optimization of aggregate functions detected constant under max() and evalueted it, but condition in the WHWRE clause (which is always FALSE) was not taken into account
Mon 2012-05-07 11:02:58 +0300
- Fix for bug
- The patch backports two patches from mysql 5.6:
  - BUG#12640437: USING SQL_BUFFER_RESULT RESULTS IN A DIFFERENT QUERY OUTPUT
Thu 2012-05-03 14:49:52 +0300
- Fix
- This is a backport of the fix for MySQL bug #13723054 in 5.6.
- Original comment:
Analysis:
- Spcifically the crash in this bug was a result of the call to key_copy() that copied the whole key, inlcuding the BLOB field which is not used for index access. Copying the blob field overwrote memory as far as the function parameter 'key_info'. As a result the contents of key_info was all 0, which resulted in a crash when this key_info was accessed few lines below in key_cmp().
Tue 2012-05-08 20:58:41 +0300
- Fix compiler warnings.
Tue 2012-05-08 19:13:26 +0300
- Addition to the fix to .
- It is problem of constant propagated to ref* access method (the problem was hiden by using debug binaries for testing).
Mon 2012-05-07 21:14:37 +0300
- fix.
- In 5.3 we substitute constants in ref access values it can't be null so we do not need add NOT NULL for early NULL filtering.

MariaDB 5.3.0 Changelog

Download |Release Notes |Changelog (page:1 [2](mariadb-530-changelog-p2.md)[3](mariadb-530-changelog-p3.md)[4](mariadb-530-changelog-p4.md)[5](mariadb-530-changelog-p5.md)[6](mariadb-530-changelog-p6.md) ) |Overview of 5.3

Release date: 26 July 2011

Revision #3134 Fri 2011-07-22 23:47:28 -0700
- Removed settings of 'derived_merge' to 'on' in ps tests.
Fri 2011-07-22 21:39:55 -0700
- Fixed a crash with pbxt.subselect when 'derived_merge' is set off in the optimizer switch.
[merge] Thu 2011-07-21 15:55:08 -0700
- Merge.
  - Thu 2011-07-21 14:23:08 -0700
    Made the optimizer switches 'derived_merge' and 'derived_with_keys' off by default.
Thu 2011-07-21 23:37:40 +0300
- Fix for
  - In case of two views with subqueries it is dificult to decide about order of injected ORDER BY clauses.
  - A simple solution is just prohibit ORDER BY injection if there is other order by.
Thu 2011-07-21 19:14:34 +0400
- : Wrong result with semijoin + view + outer join in maria-5.3-subqueries-mwl90
- Correct handling of outer joins + DuplicateWeedout (docs pending)
[merge] Thu 2011-07-21 15:50:25 +0300
- Merge from 5.2
- [merge] Thu 2011-07-21 15:21:22 +0300
  - Test fix merge.
Thu 2011-07-21 00:43:37 -0700
- Fixed .
- Do not make substitution of a single-row table if it is an inner table of an outer join with on expression containing an expensive subquery.
Wed 2011-07-20 21:55:55 -0700
- Fixed .
- An aggregating query over an empty set of a join of two tables with a rejecting HAVING clause erroneously could return a row. It could happen in the cases when the optimizer made a conclusion that the aggregating set was empty. Wrong results were produced because the server missed initial setting for aggregation functions in the mentioned cases.
[merge] Wed 2011-07-20 16:49:36 -0700
- Merge.
- Wed 2011-07-20 16:09:28 -0700
  - Fixed .
Wed 2011-07-20 16:02:26 -0700
- Adjusted the results of the pbxt.subselect test after the push of the patch for .
Wed 2011-07-20 21:48:41 +0300
- Fix of .
- ALL subquery should return TRUE if subquery rowa set is empty independently of left part. The problem was that Item_func_(eq,ne,gt,ge,lt,le) do not call execution of second argument if first is NULL no in this case subquery will not be executed and when Item_func_not_all calls any_value() of the subquery or aggregation function which report that there was rows. So for NULL < ALL (SELECT...) result was FALSE instead of TRUE.
- Fix is just swapping of arguments of Item_func_(eq,ne,gt,ge,lt,le) (with changing the operation if it is needed) so that result will be the same (for examole a < b is equal to b > a). This fix exploit the fact that first argument will be executed in any case.
Wed 2011-07-20 11:56:28 +0400
- Fix a compile error, and most likely a bug: jtb_table_no holds table number, not table->map.
[merge] Wed 2011-07-20 11:21:30 +0400
- Merge fix for
- Wed 2011-07-20 01:31:40 +0400
  - : Assertion `join->best_read < 1.7976931348623157e+308 with table_elimination=on and derived_merge=on reset_nj_counters() used to rely on the fact that join nests have table->table==NULL. This ceased to be true wit new derived table optimizations. Use test for table->nested_join!=NULL instead.
Tue 2011-07-19 23:19:10 +0300
- Fixed .
- The problem was that optimizer removes some outer references (it they are constant for example) and the list of outer items built during prepare phase is not actual during execution phase when we need it as the cache parameters. First solution was use pointer on pointer on outer reference Item and initialize temporary table on demand. This solved most problem except case when optimiser also reduce Item which contains outer references ('OR' in this bug test suite).
Tue 2011-07-19 22:22:40 +0400
- : Wrong result with semijoin=on, outer join in maria-5.3-subqueries-mwl90
- Add testcase.
Tue 2011-07-19 13:48:16 +0400
- Buildbot fixes: add --sorted-result
[merge] Tue 2011-07-19 11:45:46 +0400
- Merge
- [merge] Fri 2011-07-15 03:37:16 +0400
  - Merge
[merge] Mon 2011-07-18 23:21:48 -0700
- Merge.
- Sun 2011-07-17 23:12:31 -0700
  - Fixed .
[merge] Mon 2011-07-18 20:40:50 -0700
- Merge.
- Mon 2011-07-18 20:05:33 -0700
  - Fixed valgrind problems of the patch for bug 794901.
Mon 2011-07-18 23:45:38 +0300
- Fix
- Analysis:
  - Both the wrong result and the valgrind warning were a result of incomplete cleanup of the MIN/MAX subquery rewrite. At the first execution of the query, the non-aggregate subquery is transformed into an aggregate MIN/MAX subquery. During the fix_fields phase of the MIN/MAX function, it sets the property st_select_lex::with_sum_func to true.
[merge] Sun 2011-07-17 00:52:07 -0700
- Merge with the latest 5.3 code.
- Sat 2011-07-16 23:57:43 -0700
  - Fixed .
[merge] Fri 2011-07-15 12:16:46 +0300
- Merge of subquery cache off by default.
- Fri 2011-07-15 11:36:36 +0300
  - Make subquery cache off by default.
[merge] Fri 2011-07-15 09:17:22 +0300
- Automatic merge.
- Fri 2011-07-15 00:23:57 +0300
  - efficient partial matching
Thu 2011-07-14 22:24:59 -0700
- Changed the default setting of the optimizer switch 'optimize_join_buffer_size'. Made it 'off' by default.
Fri 2011-07-15 03:34:00 +0400
- Test result update forgotten in pre-previous cset.
Fri 2011-07-15 03:29:38 +0400
- Valgrind fix for the previous cset:
- {ha_myisam,ha_maria}::index_read_idx_map should also initialize end_range, because index condition function will attempt to check it. We initialize it like index_init() does.
[merge] Thu 2011-07-14 20:06:46 +0400
- Merge
  - Thu 2011-07-14 01:53:05 +0400
    Disable LooseScan and FirstMatch when outer joins are present.
Thu 2011-07-14 17:44:37 +0400
- Wrong result with in_to_exists=on in maria-5.3-mwl89
- Make {ha_myisam,ha_maria}::index_read_idx_map check pushed index condition.
- Address review feedback (added comments)
[merge] Wed 2011-07-13 22:19:32 -0700
- Merge.
- Wed 2011-07-13 21:06:28 -0700
  - Fixed .
Wed 2011-07-13 20:00:28 -0700
- Corrected the patch for to fix valgrind failures.
[merge] Wed 2011-07-13 12:14:35 -0700
- Merge.
- Tue 2011-07-12 23:47:35 -0700
  - Fixed .
Wed 2011-07-13 11:05:33 -0700
- Corrected the code of the recent patch that had changed the base class for Item_func_xor. Added the implementation of the subst_argument_checker virtual method that the objects of this class used to use before the patch.
- Reverted the previous result changes in sunselect_sj and subselect_sj_jcl6.
Wed 2011-07-13 16:49:52 +0400
- Update test results for previous cset
[merge] Tue 2011-07-12 13:02:19 +0400
- Merge
- Mon 2011-07-11 23:48:35 +0400
  - Port of code for: (part of testcase is in mysql-test/t/subquery*.test and will be ported separately)
Mon 2011-07-11 10:56:48 -0700
- Fixed . Auto-generated names for view field items must be allocated in the statement memory, not in the execution memory of the statement.
Sun 2011-07-10 17:19:45 -0700
- Fixed . Missing initialization of the bitmap not_null_tables_cache to 0 in the function Item_func::eval_not_null_tables caused this bug. This function is called indirectly from the function SELECT_LEX::update_used_tables after merging mergeable views and derived tables into the main query. The leaf tables of resulting query may change their bitmap numbers after this merge. That's why the not_null_tables_cache bitmaps must be updated. Due to the bug mentioned above the result of the re-evaluation of the not_null_tables_cache turned out to be incorrect in some cases. This could trigger an invalid conversion of outer joins into inner joins leading to invalid query result sets.
- Also removed an implicit conversion from int to bool in the function SELECT_LEX::update_used_tables.
[
- merge] Sun 2011-07-10 13:41:30 +0200
- merge
[
- merge] Sun 2011-07-10 13:01:00 +0200
- merge
Sat 2011-07-09 22:34:56 -0700
- Fixed . The value of THD::used tables should be re-evaluated after merges of views and derived tables into the main query. Now it's done in the function SELECT_LEX::update_used_tables. The re-evaluation of the 'used_table' bitmaps for the items in HAVING, GROUP BY and ORDER BY clauses has been added as well.
Sat 2011-07-09 16:33:40 +0400
- Semi-join fixes: make COST_VECT objects survive add_io(add_io_cnt=0, add_avg_cost=...) calls without getting NaN in internal fields.
Sat 2011-07-09 13:47:41 +0400
- [No BUG#] Fixes for problems discovered when running mysql-trunk's subquery testsuite
[merge] Sat 2011-07-09 11:20:15 +0400
- Merge @@optimizer_switch default settings changes into 5.3
- Fri 2011-07-08 22:01:02 +0400
  - Update test results for previous csets.
Scavenged subquery tests from testcases other than t/subselect*.test and put them into single file
Fri 2011-07-08 18:46:47 +0400
- Set the default to be mrr=off,mrr_sort_keys=off:
  - Set the default
  - Adjust the testcases so that 'new' tests are run with optimizations turned on.
[merge] Fri 2011-07-08 16:42:59 -0700
- Merge.
- Fri 2011-07-08 16:39:28 -0700
  - Fixed . The bug was caused by an incorrect code of the function Item_direct_view_ref::replace_equal_field introduced in the patch for bugs 717577, 724942. The function erroneously returned the wrapped field instead of the Item_direct_view_ref object itself in the cases when no replacement happened.
[merge] Fri 2011-07-08 10:56:46 +0300
- Merge test cases for bugs that were fixed by .
- Fri 2011-07-08 10:51:53 +0300
  - Test for
[merge] Thu 2011-07-07 13:06:40 -0700
- Merge.
- Thu 2011-07-07 13:04:48 -0700
  - Fixed . The offending query returns a wrong result set because the optimizer erroneously eliminated the where condition evaluated it to TRUE. The cause of this wrong transformation was that the flag maybe_null for an inner table of the outer join was not set to TRUE after the table had replaced the wrapping view. Now the function SELECT_LEX::update_used_tables resets the value of the maybe_null flag for each leaf table of the query after all merges of views have been done.
Thu 2011-07-07 16:28:26 +0300
- Fix
  - Analysis: This bug is yet another incarnation of the generic problem where optimization of the outer query triggers evaluation of a subquery, and this evaluation performs a destructive change to the subquery plan. Specifically a temp table is created for the DISTINCT operation that replaces the original subquery table. Later, select_describe() attempts to print the table name, however, there is no corresponding TABLE_LIST object to the internal temp table, so we get a crash. Execution works fine because it is not interested in the corresponding TABLE_LIST object (or its name).
[merge] Wed 2011-07-06 17:26:01 -0700
- Merge.
- Wed 2011-07-06 17:24:42 -0700
  - Fixed . The function generate_derived_keys_for_table incorrectly handled the cases when a materialized view or derived table could be accessed by different keys on the same fields if these keys depended on the same tables.
Wed 2011-07-06 21:32:07 +0300
- Adjust PBXT test results.
[merge] Wed 2011-07-06 17:27:38 +0300
- Merge the fix for
- Mon 2011-07-04 14:51:16 +0300
  - Fix
[merge] Wed 2011-07-06 10:30:51 +0400
- Merge fix for
- Wed 2011-07-06 10:21:31 +0400
  - : Crash in replace_where_subcondition with nested subquery and semijoin=on
Tue 2011-07-05 22:38:38 +0200
- fix compile warnings
[merge] Tue 2011-07-05 21:46:53 +0200
- merge Windows performance patches into 5.3
- Sun 2011-06-26 01:07:39 +0200
  - set errno to EBADF, if file descriptor < 0 in my_write()
[merge] Tue 2011-07-05 21:48:50 +0400
- Merge fix for
- Tue 2011-07-05 21:22:13 +0400
  - : Crash in pull_out_semijoin_tables with outer join + semijoin + derived tables in maria-5.3 with
Tue 2011-07-05 15:28:15 +0200
- : Remove the --innodb-release-locks-early feature.
- The exposes a design flaw in --innodb-release-locks-early. It does not work with InnoDB crash recovery, so it breaks transactional integrety. So remove the feature.
Tue 2011-07-05 10:32:49 +0400
- Update test results for the previous cset.
Tue 2011-07-05 01:44:15 +0400
- Change the default @@optimizer_switch setting fromsemijoin=on,firstmatch=on,loosescan=on tosemijoin=off,firstmatch=off,loosescan=off
- Adjust the testcases:
[merge] Mon 2011-07-04 11:02:35 -0700
- Merge.
- Sun 2011-07-03 14:59:01 -0700
  - Fixed . The assert conditions in the functions Item_direct_ref_to_ident::transform and Item_direct_ref_to_ident::compile could be not valid after constant propagation when fields and field references may be substituted for constants. Not only these invalid asserts have been removed, but the functions containing them have been removed as well because now Item_ref::transform and Item_ref::compile can be used instead of them.
[merge] Mon 2011-07-04 17:27:46 +0300
- Automatic merge
Sat 2011-07-02 17:37:59 +0300
- Fixed compilation & test issues found by buildbot
Fri 2011-07-01 21:53:47 -0700
- Fixed . If no index is used to access a materialized derived table or view then the value of TABLE_REF::key for this table must be (-1).
[merge] Fri 2011-07-01 15:35:34 +0300
- Automatic merge
- [merge] Fri 2011-07-01 15:16:10 +0300 Merge with 5.2
- Fri 2011-07-01 15:08:30 +0300
Fri 2011-07-01 13:22:23 +0400
- Buildbot run fixes:
  - update suite/pbxt/r/status.result with changes that arise from addition of Handler_tmp_% status variables.
[merge] Fri 2011-07-01 12:45:45 +0400
- Merge first chunk of OJ+SJ fixes into 5.3
- Thu 2011-06-30 20:49:11 +0400
  - Fix buildbot failures:
Thu 2011-06-30 19:32:19 -0700
- Fixed . The function generate_derived_keys_for_table should set the value of the number of keys for the derived table to 0 before it starts generating key definitions for the table. It's important as the function can be called twice by the optimizer for a derived table if the query contains a subquery to which the IN-EXIST transformation is applicable.
- Fixed a valgrind complain.
Wed 2011-06-29 20:07:24 -0700
- Fixed . If the expression for a derived table contained a clause LIMIT 0 SELECT from such derived table incorrectly returned a non-empty set.
- Fixed by ensuring JOIN::do_send_rows to be updated after the call of st_select_lex_unit::set_limit that sets the value of JOIN::unit->select_limit_cnt.

Changelog — page:1 [2](mariadb-530-changelog-p2.md)[3](mariadb-530-changelog-p3.md)[4](mariadb-530-changelog-p4.md)[5](mariadb-530-changelog-p5.md)[6](mariadb-530-changelog-p6.md)

MariaDB 5.3.3 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 21 Dec 2011

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

Revision #3367 Tue 2011-12-20 12:13:47 +0400
- Fix version number: it's 5.3.3
Tue 2011-12-20 09:57:42 +0400
- Update mysql-test/suite/pbxt/r/subselect.result for the previous push
Mon 2011-12-19 23:05:44 +0200
- Backport of from MySQL 5.6
- The patch differs from the original MySQL patch as follows:
  - All test case differences have been reviewed one by one, and care has been taken to restore the original plan so that each test case executes the code path it was designed for.
Mon 2011-12-19 22:24:10 +0400
- : EXPLAIN EXTENDED crashes in TABLE_LIST::print with limited max_join_size
  - Take into account that subquery's optimization can fail because of @@max_join_size error.
Mon 2011-12-19 20:58:55 +0400
- : Wrong result with LEFT JOIN, constant table, semijoin=ON,materialization=ON
  - Correct handling for SJ-Materialization + outer joins (details in the comments in the code)
Mon 2011-12-19 18:07:19 +0400
- Remove garbage comments
Mon 2011-12-19 10:11:21 +0200
- Supression condition made wider to cover some other system cases.
Sun 2011-12-18 23:38:37 -0800
- Fixed .
- Do not perform index condition pushdown for conditions containing subqueries and stored functions.
Sun 2011-12-18 19:25:00 +0400
- Bump version number: now it's 5.3.3 (5.3.2 has been released some time ago)
Fri 2011-12-16 08:05:14 -0800
- Adjusted test cases of the suite funcs_1.
Fri 2011-12-16 14:19:58 +0400
- Update test results for previous push
Fri 2011-12-16 10:21:46 +0400
- GIS issues fixed.
- Failures on SUN Solaris. Buggy compiler there required some extra initialization for variables. Then the 02 optimization leads to bugs when values set through the pointer are not always taken into account. Finally, the (long long) / (long) crashes there, the explicit typeconverstion added. Failing innodb_plunin.innodb_gis.test fixed.
- per-file comments:
[merge] Thu 2011-12-15 15:55:00 -0800
- Merge
- [merge] Thu 2011-12-15 14:28:34 -0800
  - Merge.
[merge] Fri 2011-12-16 03:46:04 +0400
- Merge
- Fri 2011-12-16 03:44:25 +0400
  - : Wrong result (extra row) with semijoin=ON, materialization=OFF, optimizer_prune_level=0
Thu 2011-12-15 17:26:32 +0400
- Fix unused variable 'thd' error.
[merge] Thu 2011-12-15 16:47:39 +0400
- Merge
- Thu 2011-12-15 02:49:19 +0400
  - Make MyISAM's version of create_internal_tmp_table set QPLAN_TMP_DISK, like Aria version does (otherwise slow query log would show Tmp_table_on_disk=No when it should have said Yes)
Thu 2011-12-15 16:43:28 +0400
- Fix trivial merge error
[merge] Wed 2011-12-14 20:38:38 +0200
- Merge
- [merge] Wed 2011-12-14 20:36:51 +0200
  - Merge with 5.2
[merge] Wed 2011-12-14 04:56:54 +0400
- Merge
- Wed 2011-12-14 04:39:29 +0400
  - : Crash in TABLE_LIST::print on EXPLAIN EXTENDED
[merge] Tue 2011-12-13 14:28:53 -0800
- Merge
- Tue 2011-12-13 14:20:47 -0800
  - Fixed .
Wed 2011-12-14 02:15:15 +0400
- : Crash or invalid read at st_join_table::cleanup, st_table::disable_keyread
  - Do a "more thorough" cleanup of SJ-Materialization join tab in JOIN_TAB::cleanup. The bug was due to the fact that JOIN_TAB::cleanup() may be called multiple times for the same tab if the join has grouping.
Tue 2011-12-13 20:52:06 +0200
- The variable query_cache_strip_comments allowed in embedded server.
[merge] Tue 2011-12-13 14:11:08 +0200
- Automatic merge
- Tue 2011-12-13 14:00:20 +0200
  - Fixed valgrind error when storing db_name_length in query_cache.
[merge] Mon 2011-12-12 13:00:33 +0100
- 5.2->5.3 merge
- Mon 2011-12-12 12:36:46 +0200
- Fixed
Sun 2011-12-11 19:41:53 -0800
- Fixed
- The cause of the reported assertion failure was a division of a double value by 0.
[merge] Sun 2011-12-11 14:38:14 -0800
- Merge
- Sun 2011-12-11 12:56:06 -0800
  - Fixed
Sun 2011-12-11 12:42:43 -0800
- Adjusted the results of pbxt.subselect after the latest merge 5.1->5.2->5.3.
[merge] Sun 2011-12-11 19:28:05 +0200
- Merge with 5.1 & fixes to IGNORE handling
- Sun 2011-12-11 18:39:33 +0200
  - Rewrite IGNORE handling:

constant expression"

Sat 2011-12-03 23:06:16 +0200
- Added handler and temporary table usage to mytop
- Fixed prompt on reconnect in mysql client
Fri 2011-12-09 14:30:50 -0800

Revision #3327.1.2 [merge] Sun 2011-12-11 11:34:44 +0200

Merge with 5.2.
no_error handling for select (used by INSERT ... SELECT) still needs to be fixed, but I will do that in a separate commit
Revision #2732.46.31 [merge] Sat 2011-12-03 20:47:25 +0200
- Merge with 5.1
- Sat 2011-12-03 20:29:15 +0200
  - Added suppressions
  - Fixed feedback_plugin_send to not generate a random number of lines.
Sat 2011-12-03 20:44:54 +0200
- Fixed buildbot warnings
Fri 2011-12-02 18:10:54 +0200
- Fixed some Aria limits to be more sane
[merge] Fri 2011-12-02 17:32:56 +0200
- Merge
- Fri 2011-12-02 17:22:17 +0200
  - Fixed bug where automaticly zerofilled table was not part of recovery if crash happended before next checkpoint.
Thu 2011-12-01 22:37:45 +0100
- Fix intermittently failing variables-notembedded test case.
- After sending packet that is too large, clienrt can get either an error packet with ER_NET_PACKET_TOO_LARGE, or a socket error. Both cases are valid, since the server does not ensure reply was fully read by client, before shutting down and closing the socket.
Thu 2011-12-01 20:21:11 +0200
- Fixed compiler warning
[merge] Thu 2011-12-01 20:14:53 +0200
- Merge with 5.1
- Thu 2011-12-01 20:11:41 +0200
  - Fixed that --with-libedit --without-readline works
[merge] Wed 2011-11-30 22:57:18 +0200
- Merge with 5.1
- Wed 2011-11-30 20:57:09 +0200
  - Fixed compiler warning and errors
[merge] Tue 2011-11-29 22:48:24 +0200
- Merge with 5.1 + fixes for build failures in 5.2
- Tue 2011-11-29 15:32:25 +0200
  - Fixed that maria-recover works as expected.
Tue 2011-11-29 08:50:54 +0100
- Fix testcases:
  1. main.merge fails with errno 13 in copy_file().
  2. The reason for the error is that copy_file tries to create a file with the same name as recently deleted one, and there is still an open handle for the deleted file.
Tue 2011-11-29 02:00:24 +0100
- merge, fix Windows warnings
Mon 2011-11-28 15:08:12 +0100
- after merge fixes
[merge] Thu 2011-11-24 22:48:35 +0200
- Automatic merge
- Thu 2011-11-24 19:07:36 +0200
  - Added test case for Using 'innodb_sys_indexes' causes core dump
Tue 2011-11-22 21:55:11 +0100
- fix dialog plugin to work on windows
Tue 2011-11-15 13:14:54 +0200
- Fix for sql_buffer_result=1 gives wrong result for GROUP BY with a +

Revision #3288 [merge] Thu 2011-11-17 14:27:00 +0400

merging.
Revision #2978.3.42 [merge] Sat 2011-11-12 19:56:29 +0400
- merging.
Sun 2011-10-16 21:16:53 +0500
- code cleanup.
Sun 2011-10-16 19:55:37 +0500
- GIS code cleanup.
Fri 2011-10-14 18:37:40 +0500
- #define added
Fri 2011-10-14 17:57:07 +0500
- repeating calcualtions eliminated.
Fri 2011-10-14 16:10:55 +0500
- GIS code.
- Forward calculations introduced.
- per-file comments:
Thu 2011-10-06 17:41:28 +0500
- Copyright notices fixed.
Wed 2011-10-05 14:45:39 +0500
- Valgrind warning fixed.
- Coordinate size limitation removed.
- per-file comments:
Tue 2011-10-04 15:29:39 +0500
- GIS code cleanup.
- GCALC_xxx macros fixed for the GCALC_DBUG_OFF case.
- per-file comments:
Tue 2011-10-04 15:01:21 +0500
- GIS library code cleanup.
- GCALC_DBUG_OFF and related infrastructure defined so we can enable/disable debugging conveniently.
- per-file comments:
Fri 2011-09-23 17:00:36 +0500
- Wrong result with ST_INTERSECTS and LINESTRINGs
- Line autointersection point was treated as if it doesn't belong to the line.
- It's in some way logical, but seems to confuse people. Fixed.
Fri 2011-09-23 15:36:56 +0500
- ST_WITHIN returns wrong result with MULTIPOINT and POLYGON actually only testcase added as the bug was fixed already.
- modified:
  - mysql-test/r/gis-precise.result
Fri 2011-09-23 15:25:48 +0500
- fix for ST_EQUALS returns TRUE on two nonidentical MULTIPOINTs
- The 'single point' event was forgotten in the relation's calculation
- per-file comments:
Fri 2011-09-23 15:05:36 +0500
- fix for 857050 ST_WITHIN returns wrong result with MULTIPOINT and POLYGON return GEOMETRYCOLLECTION EMPTY, not NULL for the query
- per-file comments:
  - mysql-test/r/gis.result
Thu 2011-09-22 18:53:36 +0500
- fixed bugs
  - ST_CROSSES returns different result than PostGIS for overlapping polygons
  - ST_WITHIN returns wrong result for partially overlapping polygons
Wed 2011-09-21 13:26:21 +0500
- ST_LENGTH does not work on GEOMETRYCOLLECTIONs fixed.
- per-file comments:
  - mysql-test/r/gis.result
Wed 2011-09-21 12:50:03 +0500
- fix for GIS functions return "GEOMETRYCOLLECTION()" instead of "GEOMETRYCOLLECTION EMPTY"
- per-file comments:
  - mysql-test/r/gis.result
Wed 2011-09-21 09:29:37 +0500
- bugs fixed
  - Compiler error: gcalc_slicescan.cc:2036: error: suggest parentheses around comparison in operand of .|. in maria-5.3-gis
  - ST_AREA does not work on GEOMETRYCOLLECTIONs in maria-5.3-gis
Wed 2011-09-21 00:04:41 +0500
- several bugs fixed here.
  - Second assertion `m_poly_borders->next' failed in Gcalc_operation_reducer::count_slice in maria-5.3-gis
  - Fourth assertion `n > 0 && n < SINUSES_CALCULATED*2+1' in get_n_sincos
Tue 2011-09-13 18:26:16 +0500
- Fix for Wrong result with ST_INTERSECTION between linestrings and a polygon in 5.3-gis
  - Coordinates were mistakenly reversed for MULTIPOINT.
Tue 2011-09-13 15:19:55 +0500
- Fix for Assertion `fabs(cur_isc->x-m_cur_intersection->x) + fabs(cur_isc->y-m_cur_intersection->y) < 0.000000000001' failed in Gcalc_scan_iterator::intersection_scan() in maria-5.3-gis
- That assertion's check was too tight. Released it a bit.
- per-file comments:
Tue 2011-09-13 13:59:11 +0500
- Fix for few similar bugs:
  - Assertion `t->rp->type == Gcalc_function::shape_line' failed in Gcalc_operation_reducer::end_line in maria-5.3-gi
  - Assertion `m_poly_borders->next' failed in Gcalc_operation_reducer::count_slice in maria-5.3-gis
Mon 2011-09-05 09:49:46 +0500
- Crash in Gcalc_operation_reducer::end_couple with ST_UNION and MULTIPOLYGONs in 5.3-gis.
- When edges of a polygon coicide, it can form an pike, that is turned into a line after an operation.
- In this case a former polygon point can be an end of a single line, and that case wasn't properly handled.
Mon 2011-09-05 09:13:58 +0500
- Crash in Gcalc_scan_iterator::point::get_shape with ST_DISTANCE and MULTILINESTRING in maria-5.3-gis.
  - wrong variable was used as a result of inattentive copypaste.
- per-file comments:
Sun 2011-09-04 23:48:17 +0500
- 100% CPU usage with ST_UNION in maria-5.3-gis.
  - Line loops weren't recognized when collect results.
  - Fixed by checking if we got the same beginning point of the line.
Sun 2011-09-04 19:11:04 +0500
- ST_INTERSECTION() returns invalid value on empty intersection in maria-5.3-gis.
  - We didn't implement an empty geometry. And returning NULL instead of it is not quite correct. So here is the implementation of the empty value as GEOMETRYCOLLECTION().
- per-file comments:
Fri 2011-09-02 09:38:17 +0500
- and
  - tests added.
- per-file comments:
Thu 2011-09-01 11:44:56 +0500
- PostGIS-style 'same point' handling.
Wed 2011-07-13 14:57:27 +0500
- Fix for Memory corruption/valgrind warning/crash in move_hole() with ST_UNION.
- Second smaller hole in the polygon got link to the bigger one as it's the outer ring. Fixed by specifying the outer ring explicitly.
- per-file comments:
Tue 2011-07-12 11:21:20 +0500
- Fix for Assertion `t1->result_range' in Gcalc_operation_reducer::end_couple.
  - We cannot cut a line from a polygon. So if the polygon fits the condition, and the intersection of a line and the polygon doesn't, we just skip the line.
  - That rule wasn't applied if the line start was inside the polygon, which leaded to the assertion.
Fri 2011-07-08 15:38:15 +0500
- Fix for Second assertion in Gis_geometry_collection::init_from_opresult.
  - A polygon has no right to have holes that are actually points.
  - So just skip them when we collect the result of an operation.
Thu 2011-07-07 21:30:51 +0500
- Fix for Second assertion Assertion `n > 0 && n < SINUSES_CALCULATED*2+1' in get_n_sincos.
  - Just typo-style mistake. Should be '||' instead of '&&'.
- per-file comments:
Thu 2011-07-07 16:59:45 +0500
- Fix for Assertion 0 in Gcalc_scan_iterator::pop_suitable_intersection
  - There were actually two bugs. One was when the line that intersects itself the intersection point treated as it doesn't belong to the line.
  - Second when edges partly coincide, wrong result produced when we try to find their intersection.
Tue 2011-07-05 19:42:35 +0500
- Crash in wkb_get_double with ST_INTERSECTION.
- That crash happened with the complicated topology of the result.
- If we found a hole in a polygon whose outside border was already found, we need to paste the hole right after it and respectively shift polygons after it. Also we need to update poly_position fields in these polygons. That last thing wasn't properly done that led to the crash.
Mon 2011-07-04 16:17:34 +0500
- fix for Assertion with ST_INTERSECTION on NULL values
  - The ::val_str() method has to return NULL if it calculated the null_value, not just set the related flag.
- per-file comments:
Mon 2011-07-04 16:03:36 +0500
- Infinite recursion in Gcalc_function::count_internal with ST_BUFFER over MULTIPOINT
  - Collections were treated mistakenly, so the counter for the final UNION operation received the wrong value.
  - As a fix we implement Item_func_buffer::Transporter::start_collection() method, where we set the proper operation and the operand counter. start_poly() and start_line() were also modified to function correctly for the polygon as a part of a collection.
Thu 2011-06-30 19:24:52 +0500
- fix for ST_BUFFER asserts if radius = 0.
  - Internal caclucations can't handle zero distance properly.
  - As the ST_BUFFER(geom, 0) is in fact NOOP, we'll just return the
Thu 2011-06-30 18:18:27 +0500
- fix for Assertion `(0)' failed in Gis_geometry_collection::init_from_opresult on ST_UNION
  - If the result contains a polygon with a hole, consequitive shapes weren't calculated properly, as the hole appeared as shape in the result, but actually it's a single shape with the surrounding polygon. It's more natural to use the size of the result as a border instead of the number of resulting shapes.
[merge] Mon 2011-06-20 00:21:41 +0500
- gis-related tests fixes.
- merging.
- Tue 2011-06-14 11:20:48 +0500

Revision #3274 [merge] Thu 2011-11-10 13:28:02 -0800

Merge of the maria-5.3-icp tree into the 5.3 tree
Revision #3256.1.16 [merge] Tue 2011-11-08 08:04:48 -0800
- Merge.
Mon 2011-11-07 23:30:03 +0400
- : Wrong result with ICP, outer join, subquery in maria-5.3-icp
  - Do not push index condition if we're using a triggered ref access.
[merge] Sun 2011-11-06 13:44:59 -0800
- Merge.
Sun 2011-11-06 01:23:03 -0700
- Fixed
- The bug happened because in some cases the function JOIN::exec did not save the value of TABLE::pre_idx_push_select_cond in TABLE::select->pre_idx_push_select_cond for the sort table.
- Noticed and fixed a bug in the function make_cond_remainder that builds the remainder condition after extraction of an index pushdown condition from the where condition. The code erroneously assumed that the function make_cond_for_table left the value of ICP_COND_USES_INDEX_ONLY in sub-condition markers.
Fri 2011-11-04 05:39:45 -0700
- Fixed
- The call of the virtual function cancel_pushed_idx_cond in the code of the function test_if_skip_sort_order was misplaced when backporting the fix for
[merge] Wed 2011-11-02 01:22:11 -0700
- Merge.
Tue 2011-11-01 07:00:55 -0700
- Backported the fix and the test case for from the mysql-5.6 code line.
- Fixed a bug in select_describe.
- Adjusted results for affected test cases.
Mon 2011-10-31 01:36:28 -0700
- Fixed a compilation error.
Mon 2011-10-31 01:13:12 -0700
- Backported the test case for from the mysql-5.6 code line.
- (Failed to reproduce the bug in mariadb-5.3).
Sun 2011-10-30 06:17:07 -0700
- Backported the fix and the test case for from the mysql-5.6 code line.
Sun 2011-10-30 04:18:09 -0700
- Backported the test case for from mysql-5.6 code line.
- The bug was fixed by the patches for and that were applied earlier to the mariadb-5.3 code.
Sun 2011-10-30 03:34:26 -0700
- Backported the test case for from mysql-5.6 code line.
- The bug was fixed by the patch for that was applied earlier to the mariadb-5.3 code.
Sun 2011-10-30 02:37:10 -0700
- Backported the test case for The fix was backported earlier.
Sat 2011-10-29 15:36:24 -0700
- Backported the fix and the test case for from mysql-5.6 code line.
[merge] Fri 2011-10-28 05:19:45 -0700
- Merge.
[merge] Fri 2011-10-28 04:07:11 -0700
- Merge.
- Thu 2011-06-02 14:03:02 -0700
  - Applied the patch for (for the mysql-5.6 code line).

Changelogs - MariaDB 5.3 Series

MariaDB 5.3.12 Changelog

MariaDB 5.3.11 Changelog

MariaDB 5.3.10 Changelog

MariaDB 5.3.9 Changelog

MariaDB 5.3.7 Changelog

MariaDB 5.3.5 Changelog

MariaDB 5.3.12 Changelog

Changelogs - MariaDB 5.3 Series

MariaDB 5.3.11 Changelog

MariaDB 5.3.7 Changelog

MariaDB 5.3.10 Changelog

MariaDB 5.3.9 Changelog

MariaDB 5.3.5 Changelog

MariaDB 5.3.2 Changelog

MariaDB 5.3.6 Changelog

MariaDB 5.3.0 Changelog p3

MariaDB 5.3.0 Changelog p2

MariaDB 5.3.0 Changelog p5

MariaDB 5.3.4 Changelog

MariaDB 5.3.0 Changelog p4

MariaDB 5.3.1 Changelog

MariaDB 5.3.8 Changelog

MariaDB 5.3.0 Changelog p6

MariaDB 5.3.0 Changelog

MariaDB 5.3.3 Changelog

constant expression"