Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.2.11, 10.1(EOL), 10.2(EOL)
-
centos fully patched running java connector 2.1.2
-
10.1.31, 10.2.13
Description
Our solution follows a model which maintains most of the database manipulation logic in stored procedures.
When I upgraded from 10.2.9 to 10.2.11 I immediately got a failure in existing established code. This code also continues to function on 10.1.28 without problem.
I have prepared a database dump and a script which create a repeatable error.
to avoid shipping all of the code in the database I cut down the number of procedures shipped to a minimum, and the problem is now occurring in a different procedure so it looks like a general error rather than something that is specific to a partiiuclar error in our code.
I dont want to load up the database dump onto a public web site so can I provide that separately when this bug is picked up.
I have attached below the server.cnf file, the error log associated with the current repeatable crash plus a couple of other error logs from previous tests, plus the script to generate this problem.
To recreate:
- create a database ipswichdb;
- create a user ipswichdba and essentially grant them super user administrator status to the database.
- mysql -u ipswichdb -p <ip_2018_01_02_togo.sql
- mysql -u ipswichdba -p <ip_error_gen.sql
the error files below I generated by using first deleting my current error log and then doing a systemctl restart mariadb after loading the database and before running the test script.
Also I actually run the test script in Heidi, but I get the same effect whether its hedi or a more complex java app that I am running that normally triggers the problem.
Using the 2.1.2 java connector
Attachments
Issue Links
- is duplicated by
-
MDEV-14858 MariaDB 10.1.30 Segfault
-
- Closed
-
-
MDEV-14914 MariaDB 10.2.12 crashes after midnight
-
- Closed
-
-
MDEV-15037 JOIN::optimize() crash in case of in or exists
-
- Closed
-
-
MDEV-15186 Server Crash on Subquery / Union / Temp Table in Nested Stored Proc
-
- Closed
-
-
MDEV-15187 MariaDB crashes when running a stored procedure
-
- Closed
-
- relates to
-
MDEV-15347 Valgrind or ASAN errors in mysql_make_view on query from information_schema
-
- Closed
-
The large value of thd->select_number is not garbage. It comes from sp_head::execute in sp_head.cc:
Normally the counter is not reset between parsing and first execution,
but it is possible in case of error to have parsing on one CALL and
first execution (where VIEW will be parsed and added). So we store the
counter after parsing and restore it before execution just to avoid
repeating SELECT numbers.
Other problem is that it can be more SELECTs parsed in case of fixing
error causes previous interruption of the SP. So it is save not just
assign old value but add it.
*/
thd->select_number+= m_select_number;
This was introduced in https://github.com/MariaDB/server/commit/0f43279cc472d82859960f5057e0ec98428459ee .
EXPLAIN data structure code expects select_number values to be continuous and small.