Tobias Asplund wrote:

Sven Köhler wrote:



I set the isolation level to READ_REPEATABLE and use mysqldump |
bzip2 to get the result. I've tested the restore and it's fine!


So how does mysqldump handle binary data?

If it does embed the data into the SQL-statement somehow, that's crap,
since SQL-Statements are limited in length.



On Tue, 16 Dec 2003, Chris Nolan wrote:




Are they? Shoving in rows that are several meg in size didn't pose any
problems. The restore procedure looked like this:

bunzip2 dumpfile | mysql -u db_grunt -p projectdb

May I ask where the limitation you mentioned is documented? Maybe the
situations we were using it in didn't come close to the limit.

Regards,

Chris




This is limited by the max_packet_size variable.
In 3.23.x it's limited to 16Mb, in 4.0+ it is limited by 2Gb or the amount
of physical memory the machine has, whichever is less.



I don't think any of our rows were more than 10 - 20 MB, and we were using 4.0.13 or higher the entire time.

If I recall correctly, the way around this is to use InnoDB Hot Backup for InnoDB tables and mysqlhotcopy for MyISAM tables.

I guess you're on your own for BDB tables!

Regards,

Chris

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to