Tag Info

Hot answers tagged

1

Your first HUGE mistake (as @ypercube pointed out) is not using a DATETIME type for a date-time type variable. TIMEs are not VARCHARs and doing this will mess up your queries, make your app non-portable and will confuse the optimiser. The other HUGE problem is MySQL. It doesn't perform this sort of query properly. Your query is ambiguous - PostgreSQL for ...


1

It turned out to be an issue with our Proxy Server, blocking downloads from percona.com Running sudo apt-get update revealed that every connection to percona.com 'failed', and so I got that added to the approved list, and after that it installed fine.


1

MySql doesn't support recursive functions. It supports recursive stored procedures but this feature is disabled by default. See manual. Recursion uses stack space to store contexts and tends to put memory pressure into server. I strongly discourage to use stored procedures to do this kind of calculation, better to do them into the application code. Anyway ...


1

Your question is about troubleshooting, not about 'fixing' the CPU issue. Nearly all CPU issues can be traced to bad/missing indexes or poorly written queries. Do you have the slowlog turned on? With long_query_time = 2? Can you run pt-query-digest? Well, probably you said no to all of those. Pursue them for future use. Can you do SHOW FULL ...


1

You have to use the mysql client to reload mysql -u root -p -Ddatabasename < /home/databasename_bkup.sql Another way to reload would be mysql -u root -p -Ddatabasename then from the MySQL prompt, do this mysql> source /home/databasename_bkup.sql If you would like the mysqldump to drop and recreate the database for you, create the dump like ...



Only top voted, non community-wiki answers of a minimum length are eligible