OpenSolaris OS 2008.05 is now available for download.  Its quite a departure from traditional Solaris. Why? because the CD that one will be downloading is probably just a chapter in the full book. To understand the full picture one will have to really look at the bigger picture on how the whole deployment model is now changing. The full scope is not my topic of discussion but I probably want to focus on probably couple of pieces today in order to demonstrate on how to create a PostgreSQL OpenSolaris LiveCD.

In order to create a custom LiveCD, its probably best to start with OpenSolaris OS 2008.05 installation though it is not necessary as it can be done on Solaris Express installations also but needs pkg(5) to be installed. But the two things really required to create a custom LiveCD, you need one kit to download and a repository to access. The kit to download …

Lets start at the point where you have just installed OpenSolaris OS 2008.05 and have logged in using your primary userid on the system.

First thing to do is install the packages for PostgreSQL and MySQL on OpenSolaris OS 2008.05. Right click on the desktop and select "Open Terminal" to start a terminal session. Use "su" to assume the root userid. (The primary user already has root role however some programs still explicitly check for userid of root and hence needed to avoid unexpected surprises.)

Verify pkg is able to communicate with the IPS repository.

# pkg search -r postgres …

I like Ubuntu's philosophy. Among the Debian derived Linux distros, it's the one that appeals to me the most. The first live CDs (Knoppix, Mepis) were a revolution, but Ubuntu has perfected the trend by adding a quality that was missing from these early ones.
I especially like the ease of installation. Plug to the net, apt-get install package_name, and presto! you got what you want.
MySQL server comes with just one line:

apt-get install mysql-client mysql-server

This will get you the latest server and client binaries, ready to use.
Yesterday I wanted to build MySQL 5.1 from source. The latest one (5.1.24) that has been released is missing the Federated engine, and I wanted the complete thing. So I installed Ubuntu in a spare machine, and got the source code from the development tree.
By …

While being subscribed to the full blogs.sun.com feed certainly feels like drinking water from a firehose, every once in a while I stumble over very well-written and useful articles about MySQL. Below is a collection of helpful posts, especially if you run MySQL on Solaris (surprise!). And while I still am an avid Linux user, I must admit that Solaris has a few neat features - particularly DTrace and ZFS are quite intriguing. If only userland would not feel so weird for someone coming from a GNU/Linux background!

From Jenny Chen's blog:

• DTrace Integration with MySQL 5.0 - Chime demo
…

Tolven Inc an Open Source Healthcare Solutions provider recently carried out a benchmark using PostgreSQL on Solaris 10 using ZFS on Sun Fire X4600.  The Benchmark report is now available on their website.

The size of the  single database instance using PostgreSQL 8.2.6 (32-bit) peaked at 474GB with the largest table having more than 500 million rows. More information is in the report.

Tolven's  setup guide for developers which includes information about PostgreSQL  setup is also available on their website.

As Sun SPARC Enterprise T5140 is launched along with the Open Application Services solution which includes PostgreSQL, the talk I gave at PostgreSQL East 2008 on "Best Practices with PostgreSQL on Solaris" might be helpful for many new users.

If there are questions let me know.

I started working on my upcoming talk at PGCon 2008 and realized that I haven't put my talk from PostgreSQL Conference East 2008  - PostgreSQL and Benchmarks online yet.

 More on the upcoming presentation later.

A gentle reminder: next week, there will be two more stops of the MySQL Meetup Mashup Tour:

• Monday, April 7th, 19:00: Hamburg, Germany. We will meet in the meeting rooms of the local Sun Microsystems offices ( Nagelsweg 55, 22097 Hamburg). There will be two technical sessions: Giuseppe will talk about the MySQL Sandbox, Kay Koll will give a presentation about how to combine MySQL with OpenOffice.org. He will also describe the new report generator and give an overview over the future of OpenOffice. You can register for this event via meetup.com or …

We made a very significant announcement last week, of a collaboration with one of the most (if not the most) security sensitive institutions on earth, the United States government's National Security Agency. They've joined the burgeoning OpenSolaris community, to collaborate with Sun and other community members on the future of ultra-secure operating systems.

To put this in context, community engagement has always been one of the most important ways Sun innovates in the marketplace - we partner with those that have extreme demands (whether it's the world's largest supercomputing facility, or the world's most paranoid security professionals (no offense intended), or the world's largest archival storage facilities), and then we leverage that expertise to create products for the mass market. We let extreme customers teach …

We’ve been running into a problem with one client:

SELECT COUNT(*) FROM tbl;

takes 0.25 seconds on one db, and 0.06 seconds on another.

Consistently. That’s a fourfold difference.

There aren’t any significant configuration differences (like query cache, etc.), the software versions are the same, and the table fits into memory. This has been looked at by at least 3 in-house MySQL experts, and the only thing we can determine is that it’s a hardware difference.

The table fits into memory so it’s not a disk issue, and the only other difference among the hardware is that the slower machine has Solaris virtualization in place in the form of “containers” (cpu is the same, etc). Is this something that’s known to cause issues with speed? The “tbl” in question is an InnoDB table, if that means anything. Is there something like the “speed” of RAM?

Note that Sun has already been …