1
0
mirror of https://github.com/MariaDB/server.git synced 2025-12-24 11:21:21 +03:00
Files
mariadb/mysql-test/t
Sergey Glukhov fcd99c156b Bug#11747970 34660: CRASH WHEN FEDERATED TABLE LOSES CONNECTION DURING INSERT ... SELECT
Problematic query:
insert ignore into `t1_federated` (`c1`) select `c1` from  `t1_local` a
where not exists (select 1 from `t1_federated` b where a.c1 = b.c1);
When this query is killed in another connection it could lead to crash.
The problem is follwing:
An attempt to obtain table statistics for subselect table in killed query
fails with an error. So JOIN::optimize() for subquery is failed but
it does not prevent further subquery evaluation.
At the first subquery execution JOIN::optimize() is called
(see subselect_single_select_engine::exec()) and fails with
an error. 'executed' flag is set to TRUE and it prevents
further subquery evaluation. At the second call
JOIN::optimize() does not happen as 'JOIN::optimized' is TRUE
and in case of uncacheable subquery the 'executed' flag is set
to FALSE before subquery evaluation. So we loose 'optimize stage'
error indication (see subselect_single_select_engine::exec()).
In other words 'executed' flag is used for two purposes, for
error indication at JOIN::optimize() stage and for an
indication of subquery execution. And it seems it's wrong
as the flag could be reset.
2011-10-05 13:28:20 +04:00
..
2010-02-25 23:13:11 +04:00
2011-01-25 12:14:28 +05:30
2010-03-09 16:09:32 +01:00
2009-09-29 17:38:40 +02:00
2010-12-14 12:33:03 +03:00
2011-05-04 17:12:45 +02:00
2009-05-06 15:00:14 +05:30
2009-10-20 11:00:07 -07:00
2011-03-29 10:09:05 +02:00
2010-12-14 12:33:03 +03:00
2011-03-17 16:28:16 +05:30
2010-01-29 16:54:27 +02:00
2009-08-12 12:03:05 +02:00
2011-01-26 16:50:21 +01:00
2010-10-15 20:13:35 +05:00
2009-07-03 10:19:32 +02:00
2011-08-09 11:42:07 +04:00
2009-06-10 11:58:36 +03:00