Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
10.5, 10.6, 10.11, 11.1(EOL), 11.2(EOL), 11.4, 11.5(EOL)
-
None
Description
|
11.5.0 e4afa610539ae01164485554e2de839bea9de816 (Optimized) |
11.5.0-opt>SELECT REPEAT (0,@@GLOBAL.max_allowed_packet+1); # Correct
|
+------------------------------------------+
|
| REPEAT (0,@@GLOBAL.max_allowed_packet+1) |
|
+------------------------------------------+
|
| NULL |
|
+------------------------------------------+
|
1 row in set, 1 warning (0.000 sec)
|
|
|
11.5.0-opt>SHOW WARNINGS;
|
+---------+------+------------------------------------------------------------------------------+
|
| Level | Code | Message |
|
+---------+------+------------------------------------------------------------------------------+
|
| Warning | 1301 | Result of repeat() was larger than max_allowed_packet (16777216) - truncated |
|
+---------+------+------------------------------------------------------------------------------+
|
1 row in set (0.000 sec)
|
|
|
11.5.0-opt>SELECT REPEAT (0,@@GLOBAL.max_allowed_packet); # Fails
|
ERROR 2013 (HY000): Lost connection to server during query
|
|
|
11.5.0-opt>SELECT REPEAT (0,@@GLOBAL.max_allowed_packet-1); # Fails
|
ERROR 2013 (HY000): Lost connection to server during query
|
|
|
11.5.0-opt>SELECT REPEAT (0,@@GLOBAL.max_allowed_packet-4); # Fails
|
ERROR 2013 (HY000): Lost connection to server during query
|
|
|
11.5.0-opt>SELECT REPEAT (0,@@GLOBAL.max_allowed_packet-5); # Correct
|
# Large output commences
|
Confirmed present in 10.5-11.5