MySQL - Life!

Life!

Sign in Subscribe

MySQL

A collection of 5 posts

MySQL om ZFS

It's highly recommended to provide special containers for MySQL logs and database. Personally I'm doing somethink like this, just before start database for the first time: zfs create zroot/var/mysql-db ; \ zfs create zroot/var/mysql-log ; \ zfs set recordsize=16k zroot/var/mysql-db ; \ zfs set atime=

MySQL 8.0.27 upgrade failure

If after the upgrade the mysql doesn't start don't panic! In mysql8 mysql_upgrade command is dummy, and the database upgrades automatic on first restart. In my scenario I was upgrading from 8.0.26 to mysql8.0.27 and I see errors like bellow and

Ghost and sqlite3

After many problems and outages of my blog now It is clear for me that it is better to use mysql as database backend in Ghost CMS! It looks that with Node14 it doesn't work with sqlite3 database backend. Migration is easy - just take the latest backup

MySQL command for finding all MyISAM databases, and convert them to innodb

Today most popular storage engine in latests MySQL databases is InnoDB. But if you have older databases, before the times when InnoDB becomes the king, you must somehow convert your data. You can easy find which tables are using an older storage engine using: > SELECT TABLE_SCHEMA as DbName

How-to fix Illegal mix of collations errors in mysql

If you have errors like my example bellow into your postfix logs - you can fix them easy : warning: mysql:/usr/local/etc/postfix/mysql_virtual_alias_maps.cf: query failed: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8mb4_unicode_ci,COERCIBLE) for operation '=' Get the

Share with Me via Nextcloud