Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import SQL very slow in 4.8.4 #14903

Open
WayneGit1 opened this issue Jan 25, 2019 · 9 comments
Open

Import SQL very slow in 4.8.4 #14903

WayneGit1 opened this issue Jan 25, 2019 · 9 comments
Labels
question Used when we need feedback from the submitter or when the issue is a question about PMA
Projects

Comments

@WayneGit1
Copy link

Since 4.8.4 importing sql has been very slow and invariably times out. A data file of 20MB that loaded within 60 seconds before the upgrade now fails after 300 seconds. If I break the file into 4 separate files, I can complete the import.

  • Operating system: CentOS 6
  • Web server: nginx/1.11.10
  • Database version: 5.1.73
  • PHP version: 5.6.30
  • phpMyAdmin version: 4.8.4
@MauricioFauth
Copy link
Member

What was the phpMyAdmin version before the upgrade?

@WayneGit1
Copy link
Author

4.6.6

@WayneGit1
Copy link
Author

Hi,

Were you able to reproduce the issue?

Thanks

@williamdes
Copy link
Member

@WayneGit1 Do you have Xdebug enabled ?

@musicpanda
Copy link

musicpanda commented Apr 15, 2019

I have the same problem with phpMyadmin 4.8.5.

My installation runs on Xampp under Windows 10 with PHP 5.6.

Importing a 60MB sql file took a full hour - after which a PHP timeout ended the program. When I checked all the imported tables seemed to be there. This was on a fast new computer.

When in another upload I ended MySql after more than an hour it crashed my Mysql. But it gave an interesting error message (I replaced the backticks with quotes). The empty table name suggests that something might be going wrong there.

`Error while sending QUERY packet. PID=30068 in phpmyadmin\libraries\classes\Dbi|DbiMysqli.php on line 213

ERROR

SQL query:
Select 'comment' from 'phpmyadmin'.'pma_column_info'
WHERE db_name = 'test3'
AND table_name = ''
and column_name = '(db_comment)'`

@musicpanda
Copy link

musicpanda commented Apr 15, 2019

I had a look into my Mysql error log and I found many times the following:

2019-03-24 23:52:36 28632 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-03-24 23:52:36 28632 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).

@williamdes williamdes added the question Used when we need feedback from the submitter or when the issue is a question about PMA label Jun 5, 2019
@williamdes williamdes added this to Needs triage in issues via automation Jun 5, 2019
@williamdes williamdes moved this from Needs triage to Closed in issues Jun 5, 2019
@williamdes williamdes moved this from Closed to Not reproduced in issues Sep 3, 2019
@williamdes
Copy link
Member

Is this still an issue?

@shucon
Copy link
Contributor

shucon commented Jan 25, 2021

I confirm that SQL import is very slow on PMA even after turning off XDebug on master.

@williamdes
Copy link
Member

Hi @WayneGit1
Time was passed and code has improved. Could you let me know if it works better on the latest 5.1 version in development (phpMyAdmin 5.1+snapshot) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Used when we need feedback from the submitter or when the issue is a question about PMA
Projects
issues
  
Not reproduced
Development

No branches or pull requests

5 participants