Bug #33757 mysql command line client slow when used to import a dump

Submitted: 9 Jan 2008 6:19 Modified: 9 Jan 2008 6:35
Reporter: Ralf Narozny Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S2 (Serious)
Version:5.0.52 OS:Linux (debian (Kernel 2.6.21+))
Assigned to: CPU Architecture:Any

[9 Jan 2008 6:19] Ralf Narozny 
Description:
A dump of about 142MB that was created using

mysqldump --opt --all-databases --lock-all-tables --flush-logs >dump.sql

Importing the dump on a machine imported about 50MB of data in about 30 minutes when using 5.0.52 (client and server) and took a bit 45 seconds when using 5.0.46 (on the same machine).

OS: Linux 2.6.23.12 #5 SMP Thu Dec 20 14:22:05 CET 2007 x86_64 GNU/Linux (debian)
MySQL: Ver 14.12 Distrib 5.0.52, for pc-linux-gnu (x86_64) using readline 5.1

How to repeat:
Import any large dump or set of insert statements via mysql command line client.
[9 Jan 2008 6:35] Valeriy Kravchuk 
Thank you for a problem report. Looks like a duplicate of http://bugs.mysql.com/bug.php?id=33057.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.