Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/8564/steps/test_3/logs/stdio
Also reproducible locally with ps-protocol.
$ perl ./mtr main.errors --ps-protocol
|
|
main.errors [ fail ]
|
Test ended at 2017-06-27 00:59:55
|
|
CURRENT_TEST: main.errors
|
mysqltest: At line 208: query 'select * from seq_1_to_1000' failed with wrong errno 1290: 'The MariaDB server is running with the --max-thread-mem-used=8192 option so it cannot execute this statement', instead of 1939...
|
|
The result from queries just before the failure was:
|
< snip >
|
REPLACE t2(b) SELECT '' AS b FROM t1 GROUP BY VALUES(b);
|
ERROR 42S22: Unknown column '' in 'VALUES() function'
|
UPDATE t2 SET a=(SELECT '' AS b FROM t1 GROUP BY VALUES(b));
|
ERROR 42S22: Unknown column '' in 'VALUES() function'
|
INSERT INTO t2 VALUES (1,0) ON DUPLICATE KEY UPDATE
|
b=(SELECT '' AS b FROM t1 GROUP BY VALUES(b));
|
ERROR 42S22: Unknown column '' in 'VALUES() function'
|
INSERT INTO t2(a,b) VALUES (1,0) ON DUPLICATE KEY UPDATE
|
b=(SELECT VALUES(a)+2 FROM t1);
|
DROP TABLE t1, t2;
|
#
|
# MDEV-492: incorrect error check before sending OK in mysql_update
|
#
|
CREATE TABLE t1 (a CHAR(3), b BLOB);
|
UPDATE t1 SET a = 'new'
|
WHERE COLUMN_CREATE( 1, 'v', 1, 'w' ) IS NULL;
|
ERROR 22007: Illegal value used as argument of dynamic column function
|
drop table t1;
|
set max_session_mem_used = 8192;
|
select * from seq_1_to_1000;
|
The failure appeared in 10.1 with this revision:
commit b6ce68f450ce06db989febf4dc3e2428d6400dd7
|
Author: Sergei Golubchik <serg@mariadb.org>
|
Date: Thu Jun 15 20:16:18 2017 +0200
|
|
MDEV-13012 Assertion `share->error' failed in discover_handlerton upon executing statement with max_session_mem_used = 8192
|
|
and
|
MDEV-13011 Server crashes in THD::handle_condition or Assertion `! is_set() || m_can_overwrite_status' fails upon attempt to connect with max_session_mem_used = 8192
|
|
errors when a connection is killed in the
|
* TABLE_SHARE::init_from_sql_statement_string()
|
* THD::init()
|
|
also, safety-wise, don't check max_mem_used on free() and when some error
|
was already issued.
|
Attachments
Issue Links
- relates to
-
MDEV-22422 Assertion `! is_set()' failed in Diagnostics_area::set_eof_status
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 10.1.25 [ 22542 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Assignee | Sergei Golubchik [ serg ] | Michael Widenius [ monty ] |
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Stalled [ 10000 ] |
Fix Version/s | 10.1.26 [ 22553 ] | |
Fix Version/s | 10.1.25 [ 22542 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 81382 ] | MariaDB v4 [ 152386 ] |
Reopening issue because we get in some cases the wrong error code when using max_session_mem_used.
When compiling with valgrind, this always happens.