(Note: This post is relevant only if you want to have 'DTr ace' support in the MySQL server. Packages for Solaris are available at http://dev.mysql.com/downloads/.  You can install the MySQL packages for Solaris 10 on Open Solaris)

We shall use the Sun Studio C/C++ compilers and linkers to build MySQL 6.0 alpha on Open Solaris b98 on a x86 system.

1. Grab the MySQL 6.0 alpha tarball from here
2. Extract it

3. Go to the source root, and do the following: (The text following a '#' should be treated as comments)

       $ ./configure --enable-dtrace CC=cc CXX= CC --without-falcon --prefix=/export/home/amit/mysql60-install # MySQL 6.0 alpha contains DTrace probes. To enable it use the flag --enable-dtrace, 'cc' and 'CC' are Sun C …

(Note: This post is relevant only if you want to have 'DTr ace' support in the MySQL server. Packages for Solaris are available at http://dev.mysql.com/downloads/.  You can install the MySQL packages for Solaris 10 on Open Solaris)

We shall use the Sun Studio C/C++ compilers and linkers to build MySQL 6.0 alpha on Open Solaris b98 on a x86 system.

1. Grab the MySQL 6.0 alpha tarball from here
2. Extract it

3. Go to the source root, and do the following: (The text following a '#' should be treated as comments)

       $ ./configure --enable-dtrace CC=cc CXX= CC --without-falcon --prefix=/export/home/amit/mysql60-install # MySQL 6.0 alpha contains DTrace probes. To enable it use the flag --enable-dtrace, 'cc' and 'CC' are Sun C …

(Please note that you will have to build MySQL from sources only if you want to try out the DTrace facilities. Otherwise, binary packages are available for installation) 

We shall use the Sun Studio C/C++ compilers and linkers to build MySQL 6.0 alpha on Open Solaris b98 on a x86 system.

1. Grab the MySQL 6.0 alpha tarball from here
2. Extract it
3. Go to the source root, and
   1. ./configure --enable-dtrace --prefix=/export/home/amit/mysql60-install CC=cc CXX=CC --without-falcon
      
   2. make
   3. make install

Note:

Please make sure that the location of the Sun tools are ahead in your PATH. GNU tools should be located later in the PATH. For eg.

…

I’m speaking at the MySQL European Customer Conference this week (Thursday, 23rd), on the topic of the best deployment practices for using MySQL on Solaris.

I’ll be covering a number of topics, including:

• Overview of MySQL availability on Solaris
• General tips for MySQL on Solaris
• MySQL on ZFS
• DTrace and the new DTrace Probes
• Using MySQL with containers and zones
• Using Sun Cluster and MySQL Cluster for HA

Some of the material I’ve already covered before (see my presentation at the London Solaris User’s Group, but most of the content will be new and more focused than the top level …

The newest release of Maatkit contains mk-audit bug fixes, lots of new features for mk-table-checksum so you can check replication more frequently (see my earlier post about this), and more bug fixes for other tools.

If we get enough good submissions by them, we won't extend. Meaning that if you were counting on an extension to send your proposal, it may be too late.

Of …

This poll was posted last week on Arjen’s blog and is still open for a few more days to receive your vote. The comments on the original post contain some interesting considerations either way, and many in fact non-technical. Anyway, please add your vote, and optionally your thoughts to the comment thread!

Robert Treat and I had some back and forth emails a few weeks ago about explaining database replication to customers. Replication is totally cool but it is also completely confusing to a lot of people. The basic concepts are not widely understood. Plus PostgreSQL does not help by giving you a wide range of methods, often with poorly documented trade-offs.

Based on our conversation I put together a talk for PG West in Portland called Getting Smart about the New World of PostgreSQL Replication. It explains basic concepts and surveys five replication approaches. Press the title and you can possess the slides yourself.

Robert and I had talked about putting …

Ever wonder how long that MySQL statement took to run? Or what pace those scripts you run from cron take to run at night? You can change the prompt on the MySQL command-line tool to show user name, time, current database or many other useful facts.

>mysql  foo
mysql> prompt \R:\m:\s>
PROMPT set to '\R:\m:\s>'
14:11:16>SHOW TABLES;
+------+
| foo  |
| bar  |
+------+
2 rows in set (0.01 sec)

14:12:12>

I find this quiet handy in scripts that I run late at night. It is also good when running a complex statement that will consume clock time so that I can tell when it finished. Not exactly awe inspiring but a quite handy 'trick'.



Details are here half way down the page.

Welcome to the 119th edition of Log Buffer, the weekly review of database blogs.

We start in the MySQL world with some engine news. On Brian “Krow” Aker’s Idle Thoughts, Brian explains the state of engines in Drizzle, the pared-down MySQL. He begins, “So many engines, and so little to choose from. This is one of our two major decision points in Drizzle right now.” Maria, Falcon, PBXT, and InnoDB are in the dock.

Arjen Lentz asks a simple question: Would you prefer InnoDB to be the default storage engine?, also the subject of a quick …