This has to be one of the most unexpected troubleshooting finales I've seen in a long while.
Showing posts with label Investigations. Show all posts
Showing posts with label Investigations. Show all posts
The story of MySQL Bug #86664
This is a story about why it's a good idea to test and verify the behavior of new software releases, even if the change log says that a particular bug was already fixed.
Investigating InnoDB FULLTEXT cache performance issues in MySQL <5.6.30
I'm not a huge fan of the InnoDB FULLTEXT feature and I admit I wasn't too keen to play with it in the past. Apparently, the feeling is mutual and so FULLTEXT issues haven't popped up in too many projects I worked on... until last week.
This post describes the troubleshooting process of a FULLTEXT cache performance issue. Quite inconspicuous at the beginning, it proved to be a lot of fun in the end.
Ready, Set, GDB!
This post describes the troubleshooting process of a FULLTEXT cache performance issue. Quite inconspicuous at the beginning, it proved to be a lot of fun in the end.
Ready, Set, GDB!
SHOW CREATE TABLE and foreign key constraints with innodb_read_only
The "innodb_read_only" parameter is perhaps not among the most commonly used MySQL parameters. It may however influence server behaviour in a way that you may not expect. This post is a record of an investigation that revealed one of MySQL quirks caused by said parameter.
Subscribe to:
Posts (Atom)