{"id":5754,"date":"2012-11-19T12:21:25","date_gmt":"2012-11-19T10:21:25","guid":{"rendered":"http:\/\/code.openark.org\/blog\/?p=5754"},"modified":"2012-11-19T12:23:07","modified_gmt":"2012-11-19T10:23:07","slug":"mysql-5-6-rc-further-thoughts-and-questions","status":"publish","type":"post","link":"https:\/\/code.openark.org\/blog\/mysql\/mysql-5-6-rc-further-thoughts-and-questions","title":{"rendered":"MySQL 5.6 RC: further thoughts and questions"},"content":{"rendered":"<p>Here are a few questions I came up with while experimenting with MySQL <strong>5.6.7<\/strong> &amp; <strong>5.6.8<\/strong>. They are the impressions of a first-time encounter with <strong>5.6<\/strong>, which is a single opportunity for a person to point out the things that strike as odd.<\/p>\n<p>Bugs-wise, just submitted another crashing bug for <strong>5.6.8<\/strong>. I&#8217;m just one man, so I extrapolate to realize there is still much work to be done.<\/p>\n<p>The below list does not necessarily make for a bug list; mostly things that puzzle me. I hope it can stir some additional thinking.<\/p>\n<ol>\n<li>Transportable tablespace: what&#8217;s the difference between <strong>FLUSH TABLES<\/strong> my_table <strong>WITH READ LOCK<\/strong> and <strong>FLUSH TABLES<\/strong> my_table <strong>FOR EXPORT<\/strong>? Both create the <strong>.cfg<\/strong> file, and both seem to operate just as well. <a href=\"http:\/\/blogs.innodb.com\/wp\/2012\/04\/innodb-transportable-tablespaces\/\">One document<\/a> says <strong>READ LOCK<\/strong>, <a href=\"http:\/\/dev.mysql.com\/doc\/innodb\/1.1\/en\/glossary.html#glos_transportable_tablespace\">another<\/a> says <strong>FOR EXPORT<\/strong>.<\/li>\n<li>What&#8217;s the <strong>ALGORITHM=?<\/strong> flag in online <strong>ALTER TABLE<\/strong>? Apparently one can write to altered table even on <strong>ALGORITHM=COPY<\/strong>. There&#8217;s not enough documentation to explain.<\/li>\n<li>How come there&#8217;s not a single example of online InnoDB DDL in official docs?<\/li>\n<li>Why the inconsistency of putting <strong>ALGORITHM=&#8230;<\/strong>, <strong>LOCK=&#8230;<\/strong> in between commas, as opposed to other flags\/commands not between commas? For example: <strong>ALTER TABLE my_table ADD COLUMN i INT, ALGORITHM=COPY, LOCK=SHARED, ENGINE=InnoDB ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=4<\/strong><\/li>\n<li>Why would anyone care about <strong>FULLTEXT<\/strong> search word <a href=\"http:\/\/blogs.innodb.com\/wp\/2011\/07\/innodb-full-text-search-tutorial\/\">proximity<\/a><em> by bytes<\/em>? Typically, one would want proximity by <em>words<\/em>. I can find the excuse for proximity by <em>characters<\/em>. By <em>bytes<\/em>? A user is not interested in the low level representation of the text!<\/li>\n<li>Could we get a distinct tablespace for the mysql internal InnoDB tables? (I understand there&#8217;s a separate tablespace for UNDO logs)<\/li>\n<li>Why the need to configure <strong>gtid_mode=ON<\/strong> as well as <strong>disable-gtid-unsafe-statements<\/strong> so as to enable GTID replication? If only the first is set, an error is produced upon <strong>CHANGE MASTER TO MASTER_AUTO_POSITION=1<\/strong><\/li>\n<li>And when said error is produced, why does it not mention <strong>disable-gtid-unsafe-statements<\/strong>, and instead read out a cryptic message? Also note <a href=\"http:\/\/datacharmer.blogspot.co.il\/2012\/11\/mysql-568-broken-compatibility-ahead.html\">this post<\/a> by Giuseppe Maxia.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Here are a few questions I came up with while experimenting with MySQL 5.6.7 &amp; 5.6.8. They are the impressions of a first-time encounter with 5.6, which is a single opportunity for a person to point out the things that strike as odd. Bugs-wise, just submitted another crashing bug for 5.6.8. I&#8217;m just one man, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[5],"tags":[89],"class_list":["post-5754","post","type-post","status-publish","format-standard","hentry","category-mysql","tag-new-features"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p2bZZp-1uO","_links":{"self":[{"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/posts\/5754","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/comments?post=5754"}],"version-history":[{"count":17,"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/posts\/5754\/revisions"}],"predecessor-version":[{"id":5807,"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/posts\/5754\/revisions\/5807"}],"wp:attachment":[{"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/media?parent=5754"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/categories?post=5754"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/code.openark.org\/blog\/wp-json\/wp\/v2\/tags?post=5754"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}