<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: More MySQL 6.0 news: next subquery optimizations WL pushed</title>
	<link>http://s.petrunia.net/blog/?p=50</link>
	<description>Random observations made while working on MySQL / MariaDB query optimizer</description>
	<pubDate>Sat, 04 Sep 2010 17:54:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: performance issues with sub-queries in MYSQL 5 &#8212; Able Technology - Web Application Programmers and Consultants</title>
		<link>http://s.petrunia.net/blog/?p=50#comment-51827</link>
		<pubDate>Wed, 06 May 2009 19:49:37 +0000</pubDate>
		<guid>http://s.petrunia.net/blog/?p=50#comment-51827</guid>
					<description>[...] The good news it is looks like it is fixed in version 6.0 - looking forward to it becoming a production release&#8230;. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The good news it is looks like it is fixed in version 6.0 - looking forward to it becoming a production release&#8230;. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: sergey</title>
		<link>http://s.petrunia.net/blog/?p=50#comment-40025</link>
		<pubDate>Sat, 03 Jan 2009 09:06:25 +0000</pubDate>
		<guid>http://s.petrunia.net/blog/?p=50#comment-40025</guid>
					<description>Stefan, 

The failures weren't created by this push, they were already there, see BUG#31480, BUG#37893, BUG#38015, etc. 

I don't think it's time to disable these in 6.0 yet: first,  6.0 is still alpha and second, these are *edge* cases.</description>
		<content:encoded><![CDATA[<p>Stefan, </p>
<p>The failures weren&#8217;t created by this push, they were already there, see BUG#31480, BUG#37893, BUG#38015, etc. </p>
<p>I don&#8217;t think it&#8217;s time to disable these in 6.0 yet: first,  6.0 is still alpha and second, these are *edge* cases.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Stefan Kaltenbrunner</title>
		<link>http://s.petrunia.net/blog/?p=50#comment-39953</link>
		<pubDate>Fri, 02 Jan 2009 18:48:50 +0000</pubDate>
		<guid>http://s.petrunia.net/blog/?p=50#comment-39953</guid>
					<description>Hmm - pushing a new feature to the tree that has serious known issues (ie generating wrong results for some queries seems bad) feels wrong.
Why not take a more conservative approach and disable the optimization for all the cases it is known to be wrong before the code gets enabled?</description>
		<content:encoded><![CDATA[<p>Hmm - pushing a new feature to the tree that has serious known issues (ie generating wrong results for some queries seems bad) feels wrong.<br />
Why not take a more conservative approach and disable the optimization for all the cases it is known to be wrong before the code gets enabled?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
