June 18, 2013

Post: MySQL 5.6 Compatible Percona XtraBackup 2.0.6 Released

March 20, 2013 By 2 Comments

…large increase in disk usage in cases when there are many small InnoDB… inaccessible datadir subdirectories to be ignored by XtraBackup without warning or …’t add the file-per-table setting for table-independent backups. Fixed…fixed #1085099 (Alexey Kopytov). XtraBackup for MySQL 5.6 has improved the…

Filed Under: MySQL Tagged With: , , ,

Post: Percona XtraBackup 2.1.2 for MySQL available for download

May 18, 2013 By 4 Comments

… Using Perl’s DBD::MySQL package for server communication instead of spawning the MySQL command line client … message about innobackupex –slave-info being ignored in such a case. Bug fixed #1180662. Low values … while backup is being taken. Fixed by setting the bigger value for wait_timeout option …

Filed Under: MySQL, Percona Software, Percona XtraBackup Tagged With: , , ,

Post: Ultimate MySQL variable and status reference list

January 8, 2011 By 4 Comments

…MySQL…case_file_systemblogpercona.commanual lower_case…ignore_dbblogpercona.commanual replicate_ignore…

Filed Under: Insight for DBAs, MySQL

Post: InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

March 4, 2013 By 7 Comments

…mysql: SET GLOBAL innodb_ft_server_stopword_table=’test/innodb_ft_list2′; Query OK, 0 rows affected (0.00 sec) mysql… building the word list, it’s completely ignoring Mr. Smith’s middle initial. To test … FTS configuration which are both letter-case and character-set sensitive. Watch out! When you add…

Filed Under: Insight for DBAs, Insight for Developers, MySQL Tagged With: , , , , ,

Post: Percona Replication Manager, a solution for MySQL high availability with replication using Pacemaker

November 29, 2011 By 102 Comments

…” \ no-quorum-policy=”ignore” \ last-lrm-refresh=”1322236006″ property $id=”mysql_replication” \ replication_info=”10.2.2.162|mysql-bin.000090|106″ rsc… saner behavior. One of the important setting is “log_slave_updates = OFF” (default value). In some cases, if slaves are logging replication…

Filed Under: MySQL

Post: Edge-case behavior of INSERT...ODKU

October 27, 2012 By 6 Comments

…being defined first. So, MySQL checks our INSERT, …| bar | 10 | NULL | +————+———-+———+———————+ 2 rows in set (0.00 sec) (root@localhost…, this isn’t the case. (root@localhost) [test]> select * from update_test; … all intents and purposes, ignored. For the customer …

Filed Under: Insight for DBAs, Insight for Developers, MySQL

Post: New SpecJAppServer results at MySQL and Sun.

November 12, 2008 By Leave a Comment

… does it mean MySQL did not scale well to 8 cores on this benchmark ? Now lets look at Java Settings: JDBC Pool… MySQL Settings are probably what is the most interesting: MySQL 5.0 Tuning in /etc/my.cnf (included in FDA) [mysqld] sql-mode = IGNORE… how much speed benefit did it really provide in this case. innodb_max_dirty_pages_pct=15 – Another interesting one. So…

Filed Under: Benchmarks

Post: MySQL opening .frm even when table is in table definition cache

November 21, 2011 By 8 Comments

…”the case of Stewart recognizing parameters to the read() system call …of MySQL with 100 tables and the table_definition_cache set to 1000. My understanding of this is that MySQL won… it is. We can ignore the upper limit on number of storage engines for MySQL and understanding the relationship between…

Filed Under: MySQL

Post: Percona XtraDB Cluster: Failure Scenarios with only 2 nodes

July 25, 2012 By 6 Comments

…mysql> select * from percona; +—-+—————+——–+ | id | inserted_from | name | +—-+—————+——–+ | 2 | percona1 | lefred | | 3 | percona2 | kenny | +—-+—————+——–+ 2 rows in set (0.00 sec) Adding ignore…

Filed Under: MySQL, XtraDB Cluster

Post: Improved InnoDB fast index creation

November 6, 2011 By 4 Comments

… Warnings: 0 mysql> SHOW PROFILE; +——————————+————+ | Status | Duration | +——————————+————+ . . . | copy to tmp table | 184.694432 | . . . +——————————+————+ 18 rows in set (0.00 sec) mysql> SET expand_fast… a special case of the previous one: mysql> SET expand_fast_index_creation=OFF; Query OK, 0 rows affected (0.00 sec) mysql> OPTIMIZE… would actually make the restore slower; mysqldump –innodb-optimize-keys ignores indexes on AUTO_INCREMENT columns, because they must be indexed…

Filed Under: Benchmarks, Insight for DBAs, MySQL
« Older Posts