Tag Info

New answers tagged

0

It really depends on the read-write split on your data in general. If its read heavy, then you save CPU load in RDS by smartly using query_cache. However, I would never recommend turning it to default to ON, but rather use DEMAND (number 2 in RDS parameter) that way you can use SQL_CACHE in your select statements for particularly cumbersome queries to ...


0

I have about 10 clients with same database configuration (but different versions of mysql/mariadb), and one has the same issue (mysqldump: Couldn't execute 'ROLLBACK TO SAVEPOINT sp': SAVEPOINT sp does not exist (1305)) while performing mysqldump. I am using : mysql Ver 15.1 Distrib 10.0.13-MariaDB, for Linux (x86_64) using readline 5.1 Looks like a MySQL ...


1

mysqldumpslow only works on text files, so you need to forget about using it. The table mysql.slow_log is a CSV table by default. mysql> show create table mysql.slow_log\G *************************** 1. row *************************** Table: slow_log Create Table: CREATE TABLE `slow_log` ( `start_time` timestamp NOT NULL DEFAULT ...


1

Amazon's RDS only offers PostgreSQL versions 9.3.x, and it seems unlikely that they'll ever offer to host older versions of Postgres. So by jumping from a local 8.4 install directly to RDS, you would in effect be making two significant changes at once (jumping up several Postgres versions, as well as switching to managed hosting). That may be alright or not ...


2

Try to repair the table: mysql> LOCK TABLES `fruitful_user_count` WRITE; mysql> CREATE TABLE `fruitful_user_count_new` LIKE `fruitful_user_count`; mysql> INSERT INTO `fruitful_user_count_new` SELECT * FROM `fruitful_user_count`; mysql> RENAME TABBLE `fruitful_user_count` TO `fruitful_user_count_old`; mysql> RENAME TABLE ...


2

Suggested solutions: Execute the following command REPAIR TABLE table_name; If that (step one) doesn't help try to change the temp directory in the cnf file to new location with bigger space; If step one and two did not help you need to restore the database to previous stage.


2

These two variables have nothing to do with each other. One is at InnoDB level, the other is at SQL level (and there are many engines aside from InnoDB). They may seem similar because in the case of a very crowded server they could limit the concurrency, sacrifying if for better latency. A higher value for both values (or 0, which means unlimited, for ...



Top 50 recent answers are included