Oursql-sources email group was created to discuss community MySQL builds, patches and adding features using the GPL'd version of MySQL sourcecode.

Members: 27

Discussions:

The MySQL CLA - A barrier to community contributions?
Source trees, Public Development and Builds - Version control, community contributions.

-- MarkMySQL DBA & Programming Blog by Mark Schoonover

Ask any DBA what are his top priorities for backup of MySQL. Chances are that hot backup and recovery to a specific point-in-time (or transaction) will be on top of everybody?s list.

The recovery to any point-in-time has been always an ultimate goal for data protection. Traditional backup solutions allow recovering only to a point in time when the last backup took place, e.g. last night. A lot of new data could be created and lost since that last backup. That is why in the last several years many vendors have been working on Continuous Data Protection (CDP).

Storage Networking Industry Association (SNIA) defines Continuous Data Protection (CDP) as “a class of mechanisms that continuously capture or track data modifications enabling recovery to previous points in time”.

I need to generate large (1TB-3TB) synthetic MySQL datasets for testing, with a number of requirements:

a) custom output formatting (SQL, CSV, fixed-len row, etc)
b) referential integrity support (ie, child tables should reference PK values, no orphans,etc)
c) able to generate multiple tables in parallel
d) preferably able to operate without a GUI and/or manual intervention
e) uses a well defined templating construct for data generation
f) preferably open source

Does anyone out there know of a product that meets at least most of these requirements?

*edit*
I found a PHP based data generation script (www.generatedata.com) that is extensible in its output formatting, so it should do everything I need it to do.

I just left a meeting with a large enterprise that dumped Microsoft Sharepoint for Alfresco for content management and collaboration. While that makes me smile, the thing that I loved hearing most from the vice president of IT was her general thoughts on open source, and why it's getting more play within this media company, including Alfresco, MySQL, Liferay, and more:

The culture here is about freedom and the ability to impact things ourselves. We're adopting more and more open source because we want to be in control of our own destiny....

In some cases, open source has meant higher implementation costs upfront but lower costs over the long run.

There is a resistance here to being framed into a long-term proprietary path: Closed APIs, closed standards, and closed source force us onto a vendor's licensing treadmill - we don't want that. We want flexibility and choice. We think about IT for the long run.

Music to …

Jonathan Schwartz of Sun, and Giuseppi Maxia of MySQL
Originally uploaded by FallenPegasusAccording to my Flickr stats, this picture just got a huge surge of views, most of them from "fakesteve.blogspot.com".

But when I go to that blog, I can't find the link.

Can anyone find it for me?

I'm pleased to announce the release of DBD::mysql 4.007. This release contains the changes:

* Took out mysql_server_init call where not needed
* Complete re-write of test suit to use Test::More - tons of cleanups!
* Makefile.PL changes to use current user in 'make test' if not defined

The biggest change in this release is a completely re-written test suite now using Test::More. This was something I wanted to do for at least two years. Using Test::More for the test suite makes it so much easier to add, manage and understand the various tests that come with the driver.

The file is:

file: $CPAN/authors/id/C/CA/CAPTTOFU/DBD-mysql-4.007.tar.gz
size: 123516 bytes
md5: 67a4d921acda942aeb0e65a0023f2098

URL:
http://search.cpan.org/~capttofu/DBD-mysql-4.007

…

Properties:

Description:

This variable if enabled, makes InnoDB to create a separate .ibd file for storing indexes and data. Setting this variable makes it easy to manage disks with huge tables. Having …

I have always considered MySQL as the best model for open source companies. Their approach to the market, the execution of different business models, their relation with the community or the way their work internally as a virtual organization have shown an innovative and successful example of how an IT company in the 21st century can be managed.

The agreement with Sun, announced last January, was the crowning point of all the efforts put in the company since the beginning, proving the success of their innovative model. Since then I have been trying to put some order in my ideas about their model and summarize them in a few blocks that could serve as a quick guide to emulate their success. I discussed my ideas with Henrik Ingo, a friend of mine …

So, remember last month when there was all that furor over the apparent move by MySQL to start making some bits and pieces of the hugely popular open source database over into close source? (Here, Clarifying the MySQL "Closed-Sourcing" brouhaha, for example.)

Well, er, it turns out that the correct answer is: "Never mind."

Per Kaj Arno, MySQL VP Community, MySQL Server is Open Source, even Backup extensions.

You can get the Slashdot crowd's viewpoint here, MySQL Reverses Decision On Closed Source.

Much as I like to rationalize and "support" open source vendor policies, no matter how ill-conceived, …

Recently I ran into major problems using GNU diff. It would crash with "diff: memory exhausted" after only a few minutes trying to process the differences between a couple 4.5GB files. Even a beefy box with 9GB of RAM would run out of it in minutes.

There is a different solution, however, that is not dependent on file sizes. Enter rdiff – rsync's backbone. You can read about it here: http://en.wikipedia.org/wiki/Rsync (search for rdiff).

The upsides of rdiff are:

• with the same 4.5GB files, rdiff only ate about 66MB of RAM and scaled very well. It never crashed to date.
• it is also MUCH faster than diff.
• rdiff itself combines both diff and patch capabilities, so you can create deltas and apply them using the same program

The downsides of rdiff are:

…