mariadb/mysql-test/r/mysql-bug45236.result at 5cf5a9a1e8660cbcc60362d90cc22b63b2c05ed7 - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-16 03:52:35 +01:00

Alexey Kopytov 897a1b56d8 Bug #45236 : large blob inserts from mysqldump fail, possible

memory issue ? 
 
The mysql command line client could misinterpret some character 
sequences as commands under some circumstances. 
 
The upper limit for internal readline buffer was raised to 1 GB 
(the same as for server's max_allowed_packet) so that any input 
line is processed by add_line() as a whole rather than in 
chunks.

client/mysql.cc:
  The upper limit for internal readline buffer was raised to 1 GB 
  (the same as for server's max_allowed_packet) so that any input 
  line is processed by add_line() as a whole rather than in 
  chunks.
mysql-test/r/mysql-bug45236.result:
  Added a test case for bug #45236.
mysql-test/t/mysql-bug45236.test:
  Added a test case for bug #45236.

2009-06-10 11:24:47 +04:00

8 lines

329 B

Text

Raw Blame History

 DROP TABLE IF EXISTS t1;
 SET @old_max_allowed_packet= @@global.max_allowed_packet;
 SET @@global.max_allowed_packet = 1024 * 1024 + 1024;
 CREATE TABLE t1(data LONGBLOB);
 INSERT INTO t1 SELECT CONCAT(REPEAT('1', 1024*1024 - 27),
 "\'\r dummydb dummyhost");
 DROP TABLE t1;
 SET @@global.max_allowed_packet = @old_max_allowed_packet;