Re: [Maria-developers] MariaDB 5.2.5
On Thu, 03 Mar 2011 18:18:05 +0100 Jocelyn Fournier wrote: Jocelyn> Hi, Jocelyn> Jocelyn> The following paths in the Bug Fixes section of the release Jocelyn> note http://kb.askmonty.org/v/mariadb-525-release-notes are Jocelyn> wrong : Jocelyn> Jocelyn> http://kb.askmonty.org/v/mariadb-5.2.5-changelog Jocelyn> http://kb.askmonty.org/v/mariadb-5.1.55-changelog Fixed. Thanks! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
Re: [Maria-developers] MariaDB 5.2.5
Hi, The following paths in the Bug Fixes section of the release note http://kb.askmonty.org/v/mariadb-525-release-notes are wrong : http://kb.askmonty.org/v/mariadb-5.2.5-changelog http://kb.askmonty.org/v/mariadb-5.1.55-changelog Regards, Jocelyn Fournier Le 03/03/2011 18:05, Daniel Bartholomew a écrit : Here are the download, release notes, and changelog pages for 5.2.5: * http://downloads.askmonty.org/mariadb/5.2.5 * http://kb.askmonty.org/v/mariadb-525-release-notes * http://kb.askmonty.org/v/mariadb-525-changelog If any of you have a moment, please check over the above pages to see if there are any mistakes or omissions and let me know (or jump in and fix if you have editing rights). Community team: I tested a sample of the mirrors and they all had the files so please announce the release on the announce list, blogs, and so on. Thanks. ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
[Maria-developers] MariaDB 5.2.5
Here are the download, release notes, and changelog pages for 5.2.5: * http://downloads.askmonty.org/mariadb/5.2.5 * http://kb.askmonty.org/v/mariadb-525-release-notes * http://kb.askmonty.org/v/mariadb-525-changelog If any of you have a moment, please check over the above pages to see if there are any mistakes or omissions and let me know (or jump in and fix if you have editing rights). Community team: I tested a sample of the mirrors and they all had the files so please announce the release on the announce list, blogs, and so on. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
Re: [Maria-developers] [Commits] Rev 2929: Fix LP BUG#718763 in file:///home/tsk/mprog/src/5.3/
Hi!
Everything looks OK, except one small style error.
Also it would be nice to put somewhere 'TODO:' to bring in order
'uncachable' flags.
On 03.03.2011 14:07, tim...@askmonty.org wrote:
At file:///home/tsk/mprog/src/5.3/
revno: 2929
revision-id: tim...@askmonty.org-20110303120726-la5o40rldim2t93y
parent: pser...@askmonty.org-2011030107-1rmapkelx9l1kw8u
committer: tim...@askmonty.org
branch nick: 5.3
timestamp: Thu 2011-03-03 14:07:26 +0200
message:
Fix LP BUG#718763
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.
Solution:
In the methods Item_in_subselect::[single | row]_value_transformer() set:
select_lex->uncacheable|= UNCACHEABLE_EXPLAIN;
In addition, for symmetry, change:
master_unit->uncacheable|= UNCACHEABLE_EXPLAIN;
instead of UNCACHEABLE_DEPENDENT because if a subquery was not
dependent initially, the changed methods do not change this
fact. The subquery may later become correlated if it is transformed
to an EXISTS query, but it may stay uncorrelated if executed via
materialization.
[skip]
@@ -1742,7 +1752,15 @@ Item_in_subselect::row_value_transformer
optimizer->keep_top_level_cache();
thd->lex->current_select= current;
-master_unit->uncacheable|= UNCACHEABLE_DEPENDENT;
+/*
+ The uncacheable property controls a number of actions, e.g. whether to
+ save/restore (via init_save_join_tab/restore_tmp) the original JOIN for
+ plans with a temp table where the original JOIN was overriden by
+ make_simple_join. The UNCACHEABLE_EXPLAIN is ignored by EXPLAIN, thus
+ non-correlated subqueries will not appear as such to EXPLAIN.
+*/
+master_unit->uncacheable|=UNCACHEABLE_EXPLAIN;
+select_lex->uncacheable|= UNCACHEABLE_EXPLAIN;
if (!abort_on_null&& left_expr->maybe_null&& !pushed_cond_guards)
{
put space (' ') after '='
[skip]
___
commits mailing list
comm...@mariadb.org
https://lists.askmonty.org/cgi-bin/mailman/listinfo/commits
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help : https://help.launchpad.net/ListHelp
