Installing Lighttpd With PHP5 And MySQL Support On Fedora 12

Lighttpd is a secure, fast, standards-compliant web server designed for speed-critical environments. This tutorial shows how you can install Lighttpd on a Fedora 12 server with PHP5 support (through FastCGI) and MySQL support.

Here are the minutes of the meeting. They can also be found online
with the irc logs here.

Review ACTION points from previous meeting

• kirkland to publish tentative bugzapping roadmap: Done, will be updated.

Beta1 status review

ttx informed everyone that we are at the beginning of the beta1 subcycle… but not very far from the end of it. Thursday next week is Beta1Freeze, a hard freeze before the Beta1 release, so most uploads should be made before that date. For reference, the beta1-targeted blueprints are tracked at http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html

smoser reported …

One of my colleagues, Ryan Lowe, has just heard that his session on PCI compliance with MySQL has been accepted at the upcoming MySQL conference. Ryan is highly qualified to present this topic, and not many people can say that; I certainly can’t claim that title myself. If you’re looking to learn how to make your MySQL installation PCI-compliant, there’s also not a lot of trustworthy information online. Personally — and really, no bias just because he’s my colleague — I think this is a great session for the MySQL conference, which I sometimes thought didn’t have enough diversity of topics in past years. We need more stuff like this to give people a reason to return after they’ve gone for 2 or 3 years in a …

In Oracle the default transaction isolation is READ_COMMITTED. In MySQL the default is REPEATABLE_READ. Because MySQL also has READ_COMMITTED I have seen in more then one production MySQL environment a transaction isolation of READ_COMMITTED. The explanation and ultimately incorrect assumption is the default in Oracle is READ_COMMITTED so we made that the default in MySQL.

I’m not going to discuss the specific differences of these isolation levels (see reference lines below) except to say it that READ_COMMITTED in Oracle more closely relates to the MySQL default of REPEATABLE_READ and not READ_COMMITTED. Just because the same term for a common feature exists, don’t assume the underlying functionality is the same or that either or both actually conform to the SQL ANSI standard.

While switching your MySQL environment to READ_COMMITTED is possible, there is still conjucture if this actually provides any performance improvement. …

Its times like this, I want to hear from the greater community – the ones that are reading say, Planet MySQL or Planet MariaDB.

MySQL to me, and many others is an ecosystem. We’ve had for the longest time, complementary technology talks, like for memcached (which have been popular, filled rooms). NoSQL is becoming quite popular, and there are complementary technologies sitting around. To get an idea, if terms like the following turn you on: Hadoop, Redis, Pig, NDB (yes, MySQL Cluster is largely NoSQL before NoSQL became popular), Tokyo Tyrant, StormCloud (formerly Waffle Grid).

Now, do you want to see these kinds of talks at the MySQL Conference & Expo 2010?

Check out the …

As promised, we are pleased to announce the availability of the 1.0.3 release of InfiniDB Community Edition.  This is the first of our monthly maintenance releases that are scheduled throughout the spring.

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.   We have also included support for prepared statements with bind variables and a performance improvement for queries that select many columns with neRead More...

CMake is a cross-platform, open-source build system, maintained by Kitware, Inc.

From the CMake.org home page:

CMake is a family of tools designed to build, test and package software. CMake is used to control the software compilation process using simple platform and compiler independent configuration files. CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice.

It has been used for building the MySQL Server on Windows since MySQL 5.0 – the initial CMake build support was added in August 2006.

For …

So after I published my patch last night, another of my colleagues - the esteemed Shane Bester - pointed out that there is a related bug - Bug#28405 - which requests that Com_change_user is also split out from Com_admin_commands.

So I extended my patch this morning, to kill two birds with one stone:

=== modified file 'sql/mysqld.cc'
--- sql/mysqld.cc       revid:alik@sun.com-20100114090008-3rsdmlp1w2mqgrhg
+++ sql/mysqld.cc       2010-03-03 09:57:40 +0000
@@ -3131,6 +3131,7 @@
   {"call_procedure",       (char*) offsetof(STATUS_VAR, com_stat[(uint) SQLCOM_CALL]), SHOW_LONG_STATUS},
   {"change_db",            (char*) offsetof(STATUS_VAR, com_stat[(uint) SQLCOM_CHANGE_DB]), SHOW_LONG_STATUS},
   {"change_master",        (char*) offsetof(STATUS_VAR, com_stat[(uint) SQLCOM_CHANGE_MASTER]), SHOW_LONG_STATUS},
+  {"change_user",          (char*) offsetof(STATUS_VAR, com_change_user), …

Right now, we support InfiniDB on a couple of different Linux flavors. As we march toward a couple of more releases this year, we want to expand our operating system support. We could really use your input on which OS's we should support next. Please go to http://www.infinidb.org/index.php. On the lower left corner you'll see our OS poll - please vote and let us know which OS you use for your production databases. Thanks!

I've been making some improvements to our use of Hudson recently that have been really helpful.

The first was starting to use a set of parameterized builds. These use the Parameterized Trigger plugin, which allows you to pass parameters to triggered additional jobs when a job finishes. So using these we make a job which checks out the latest source (which should just about always succeed) and then fire off a whole host of jobs running on all of our build hosts. It has a single "build now" submit form which takes a bzr branch location as the branch to build. With this all of our developers can check their tree against the build farm before submitting the branch for merge.

That's great, but as we got more and more build hosts, we had to set up a job on each of them - and then having 4 machines which were all amd64 running Ubuntu 9.10 …