- mySQL stores executed SELECT statements and its results in query cache
- if the same statement is executed again, results are taken from cache
- controled by parameter ”
query_cache_size“
Recent Posts
- How to clean or resize the ibtmp1 file in MySQL
- Check MySQL slow log from command line
- Relay log read failure: Could not parse relay log event entry – binary log is corrupted
- How to change data type of column used in foreign key
- Tiny fun with TINYINT data type
- How to handle errcode 28 – no space left
- What can happen when you try to use very big VARCHAR columns
- Message “Could not increase number of max_open_files” in MySQL error log
- MySQL 5.7 parameter range_optimizer_max_mem_size
- Setting MySQL chain replication
- MySQL memory usage / settings
- Problems with remote login into MySQL caused by performance_schema tables
- How to handle heavy changes in MySQL replication with ansible
- Error ‘You cannot ‘ALTER’ a log table if logging is enabled’ on query. Default database: ‘mysql’. Query: ‘ALTER TABLE slow_log
- Switch the binlog format at runtime
- Bash script – restore non-replica from data files backuped with Percona XtraBackup
- MySQL replication troubleshooting – replication error on replica
- Bash script: create backup with Percona XtraBackup
- Clone database with Percona xtrabackup
- Experiences with tuning of MySQL 5.7 replicas
- Move MySQL data files / log files / temp directory to the different disk on Ubuntu / Debian
- Create new replica by copying data and log files on OS level
- Global status – table open cache
- Global status – tmp tables
- Linux hugepages and MySQL – Ubuntu / Debian
Categories
- Ansible (3)
- Backup + Restoration (3)
- Data manipulations (1)
- Database design (4)
- Global Status (2)
- information_schema (2)
- Locks (1)
- mySQL on Linux (1)
- Performance (9)
- Replication (14)
- Settings (4)
- Storage engines (4)
- Transactions (6)
- Troubleshooting (9)
- Useful small hints (4)
- Usefull scripts (3)