<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="0.92">
<channel>
	<title>Sergey Petrunia's blog</title>
	<link>http://s.petrunia.net/blog</link>
	<description>Random observations made while working on MySQL / MariaDB query optimizer</description>
	<lastBuildDate>Tue, 16 Feb 2010 20:02:55 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>MariaDB at FOSDEM: slides, booth questions, etc.</title>
		<description>At FOSDEM 2010, MariaDB was represented by Kristian Nielsen and me. Together with Vlad Kolesnikov we've manned the joint MariaDB & PBXT stand. I've had the main track talk titled "MariaDB: extra features that make it a better branch of MySQL" (slides), and 
Kristian had a more general talk titled ...</description>
		<link>http://s.petrunia.net/blog/?p=60</link>
			</item>
	<item>
		<title>Ongoing MariaDB development: filtering and rewrites in mysqlbinlog</title>
		<description>The main focus of MariaDB staff has been the MariaDB 5.1.38 release in recent weeks, but this doesn't mean that we've abandoned everything else for it. There are several non-release projects going on, one of which is adding binlog filtering and markup capabilities.

In order to see how the new features ...</description>
		<link>http://s.petrunia.net/blog/?p=59</link>
			</item>
	<item>
		<title>MariaDB 5.1 feature: Table Elimination</title>
		<description>MariaDB 5.1 beta is almost out, so it's time to cover some of its features.  The biggest optimizer feature is MWL#17 Table Elimination.

The basic idea behind table elimination is that sometimes it is possible to resolve the query without even accessing some of the tables that the query refers ...</description>
		<link>http://s.petrunia.net/blog/?p=58</link>
			</item>
	<item>
		<title>Added a copy of mainline mysql-5.1 into our Buildbot</title>
		<description>And it has failed the testuite on every single build slave. I've filed BUG#45605, BUG#45630 (together with a patch), BUG#45631, BUG#45632. There is also rpl.rpl_innodb_bug28430 test failure which I didn't report as I don't yet have enough details about the build slave.

At the moment our setup works as follows: there ...</description>
		<link>http://s.petrunia.net/blog/?p=57</link>
			</item>
	<item>
		<title>Test failures in 5.1, different people making different fixes for the same problem</title>
		<description>This is what's happening at the moment. 5.1 tree doesn't pass the tests, both Sun and Monty Program fix that, and the fixes are different. Here is a Valgrind warning which was fixed twice: my fix my fix (correct link) made the involved mysys function to do what its name ...</description>
		<link>http://s.petrunia.net/blog/?p=56</link>
			</item>
	<item>
		<title>Changed jobs, now at Monty Program AB</title>
		<description>This isn't news anymore - it has been over a month - but it would be odd not to mention this all, so here it goes: at the start of May I've left Sun Microsystems and joined Monty's company.

The setup at Monty Program AB is quite similar - we have ...</description>
		<link>http://s.petrunia.net/blog/?p=55</link>
			</item>
	<item>
		<title>Notes from Feature Request Bonanza session at Percona Performance conference</title>
		<description>I was taking notes during "Open Q&A: Feature Request Bonanza" session at the Percona Performance conf. The session started at 9 pm at the last day of the conference, so the room wasn't as full as it was for other sessions, but still there was an interesting discussion. I've missed ...</description>
		<link>http://s.petrunia.net/blog/?p=54</link>
			</item>
	<item>
		<title>Optimizer news: @@optimizer_switch syntax changes and backport</title>
		<description>In short, the news are:

@@optimizer_switch support was backported into MySQL 5.1
The switch syntax was changed from 'no_optimization_name' to 'optimization_name=on&#124;off&#124;default'.
Added switches for index_merge, index_merge_intersection, index_merge_union, and index_merge_sort_union optimizations.


The changes will be available in next releases, that is, MySQL 5.1.34 and 6.0.11.
Now with more details:
New switch names
Until now, the syntax mimicked an ...</description>
		<link>http://s.petrunia.net/blog/?p=52</link>
			</item>
	<item>
		<title>Sun Tech Days St. Petersburg 2009</title>
		<description>Sun Tech Days St. Petersburg was on Wednesday-Thursday the last week and we've had a MySQL booth there. Unlike the last year, we're full part of Sun now so managed to get a decent-sized booth, arrange for leaflets, and Kostja gave an overall MySQL talk.


Questions at the booth (in no ...</description>
		<link>http://s.petrunia.net/blog/?p=51</link>
			</item>
	<item>
		<title>More MySQL 6.0 news: next subquery optimizations WL pushed</title>
		<description>Three days ago I've finally managed to push the code for WL#3985 "Subquery optimization: smart choice between semi-join and materialization" into MySQL 6.0. I missed the clone-off date so it won't be in the upcoming MySQL 6.0.9 release, the only way to get it before the next 6.0.10 release is ...</description>
		<link>http://s.petrunia.net/blog/?p=50</link>
			</item>
</channel>
</rss>
