WFTO – Weekly Falcon Test Overview 2009-04-24

WFTO – week of MySQL Conference & Expo 2009

This week with our MySQL Conference & Expo 2009 happening, we traditionally
saw low development activity. We will continue our interview series with
Lars-Erik Bjørk.

lars-erik

WFTO interview with Lars-Erik Bjørk

Q: Hi Lars-Erik. May you introduce yourself in two or
three sentences? Personally I would like to know whether
Bjørk, your older sister is OK so far and why you gave up
being the lead singer of A-HA.

Lars-Erik:
I am a 27 year old Norwegian that joined the Falcon team from Sun Microsystems.
Before working on Falcon I worked on HADB (the Clustra database).
The most common question asked to me by strangers actually is:
“Are you related to Björk?”. The first 50 – 60 times I answered “No”, but
lately I have started to answer “Yes”, just for the fun of it.
As revealed by Chris Powers, I used to be a part of the group A-HA.
When the music video for the hit “Take on Me” was recorded in 1984/1985,
I was actually just two years old, but thanks to advanced graphical
manipulation, we managed to pull it off. As Chris said, I quit the band to
pursue a career in software engineering 🙂

Q: In the last months we saw a lot of bugfixes
from you in the index area. I heard that indexes in Falcon have a
kind of prefix-compression. Can you enlighten us a bit about it?

Lars-Erik:
In an index, the keys are ordered, and keys close to each other typically have
identical leading bytes. When this is the case, there is no need to store the same
leading bytes in every of these keys. Instead we store one or two prefix-bytes
that tell how many leading bytes that are identical to the leading bytes of the
preceding key. These bytes are suppressed by prefix compression. This allows
us to store more index nodes on a page, have a bigger fan-out and a lower index tree.

the_dog

Q: On IRC we see you sometimes being busy
walking your dog. We at Falcon would love to see a picture
of you and your dog! Can you provide us one?

Lars-Erik:
This is 2.8 kilos of pure Chihuahua. His name is Romeo, and he is a ladies man.
He loves ladies of all sizes and shapes. It is important to know that Paris Hilton
takes after us, not the other way around (seriously) 🙂

Q: I recall some bugfixes of you in the area of
Falcon’s encode/decode mechanism. Can you give a brief overview
what the idea about encode/decode is and how it is done in Falcon?

Lars-Erik:
I am certainly no expert on Falcon’s record encoding, and I actually had to
cheat and look at the docs when I got this question, but I can try to say a few sentences about it 🙂

For records in the memory-resident record cache and on disk, Falcon uses a variable
length data encoding that depends on the stored values, and not on the type of the
field. For example, the MySQL data types tiny, short, int, year and some others,
are all represented as unscaled integers. And all null-valued fields are represented
by the same type byte regardless of the type of the field. This encoding saves space,
but makes it impossible to reference a field in the record directly without doing some
processing of the previous fields in the record, as there is no way of knowing the offset
of the field. Therefore, we keep an index of the offsets for the fields we have visited, so
we don’t need to do the same calculations twice.

Eliminating excess space in this way, allows us to do less I/O, which is the real
performance killer in a DBMS. However Kelly Long has discovered that quite a few
cycles are spent doing encode/decode, so it may be that the strategy must be revisited
to squeeze out some additional performance.

Q: Thank you very much for your detailed answers!
Lars-Erik: You’re welcome.

Now back to our usual report: it was MySQL Conference & Expo 2009 and our developers
were busy at the conference.

Since my last report from 2009-04-17 we fixed around 3 Falcon related bugs.
Compared to our last WFTO from 2009-04-17 we have one new test.

The development of our failed/passed tests ratio over time looks like:

  • 0.39% – 1/254(this report)
  • 0.40% – 1/253 (last report)
  • 1.20% – 3/249 (report before last one)

weekly_falcon_test_overview_2009-04-24

News for this week:

  • Vladislav Vaintroub fixed
    • Bug#36993 Falcon reports Index SCHEDULE..PRIMARY_KEY in SYSTEM.SCHEDULE damaged
    • Bug#41840 Unbounded tablespace growth during recovery
    • Bug#43106 Falcon recovery assertion (bdb->buffer->pageNumber == pageNumber) in Cache.cpp

The failing test case is

  • falcon_deadlock (known issue)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | 1 Comment

WFTO – Weekly Falcon Test Overview 2009-04-17

WFTO – mid of April report

in my next reports I will interview my MySQL/Falcon team members. This week we start with
Vladislav Vaintroub, who is Russian but lives in Germany.  He is well known to speak at least
twenty-two foreign langauges, many of them English.

vlad_athens_2009

WFTO interview with Vladislav “Wlad” Vaintroub

Q: Hi Wlad. May you introduce yourself in two or
three sentences? Personally I am wondering why
your nick is Wlad instead of Vlad.

Wlad:
That’s simple : I use the IRC nick “wlad”, because when I joined MySQL “vlad”
was already taken by another MySQLer called Vladislav Safronov. In the past,
German government agencies gave me the name Wladislav and people knew me
as Wlad, during naturalization of the Cyrillic alphabet they changed that to Vladislav,
and now people know me as Vlad.

For myself I still like Владислав/Влад better and frankly do not care that much
about how it is latinized.

Q: In the last months we saw a lot of bugfixes
from you in the recovery area. Can you explain
Falcon’s recovery strategy a bit. I heard that
the recovery in Falcon has several distinct stages.

Wlad:
I am probably not the best person to ask about Falcon’s recovery as I did not design it.
All I have done is just fixing glitches in it for about three months, which is not really a
long time.

But if you want a simplistic view on it, then …

Falcon recovery is REDO-recovery – it has no UNDO phase. Falcon uses deferred updates
and until transaction commits and is completely recorded into log, nothing is changed
in its tablespaces.

There are 2 types of database log records “physical”: log creation of tablespaces,
page allocations and similar things, and “logical”: actual records and index entries.

The recovery is divided into 3 stages.

1) Determine what changes need to be reapplied.
An interesting detail in this process is something called “incarnations” in Falcon.
An illustration for this concept:

If a page N was allocated as index page, then freed during drop index and then
reallocated and reused as data page, then there are 3 different states of the
same page stored in the log (index, free, and data). Only the last state needs
to be considered, and some efficiency can be achieved by skipping prior
“incarnations” of this page.

2) Re-apply “physical” changes.
Pages are reallocated, and tablespaces recreated. Index pages are stored in and
restored from the log in “after split” state: this guarantees that Btrees are
valid after this phase. Pages with the last incarnation before the last checkpoint
are not recreated – it is a performance tweak.

3) Re-apply “logical” changes.
Store records and index entries in pages.

This stage is very similar to what Falcon does also during normal processing:
on commit, records and index entries found on different in-memory caches are
written to the log and background thread will bring them into tablespace pages.

Interesting to note is that recovery itself does not write log entries, and
that means changes done in phases 2 and 3 need to be idempotent to allow
recovery after a crashed recovery.

Q: I understand that you and Philip Stoev developed
an error injection mechanism to forcefully crash mysqld
at interesting parts of the code. You put some error
injections into Falcon’s recovery code to make critical
code paths even more robust. Can you explain us how the
error injection works, show us some code, and give us an
example about how one could crash Falcon at home?

Wlad:
Unfortunately I could not convince Philip to a debugger based scripting/automation:
set breakpoints on interesting places and then crash when breakpoints are reached.
So error injection was born. There is already a similar mechanism within the
MySQL core server based on DBUG macros (DBUG_EXECUTE_IF?)

Falcon’s one has some flexibility and adds a parameter and iteration counts to
injection points.

To see it in action, try in mysql client.

  CREATE TABLE t (i int) Engine Falcon;
  SET GLOBAL falcon_error_inject='type=SerialLogAppend,param=2,iterations=2';
  INSERT INTO t VALUES (0);
  INSERT INTO t VALUES (0);

the last query will crash with

  ERROR 2013 (HY000): Lost connection to MySQL server during query

The cryptic “type=SerialLogAppend,param=2,iterations=2” means: crash when serial
log entry with id 2 (srlCommit) is written for the second time. In the test we
insert twice in autocommit mode, causing two srlCommits and second one kills
the server.

Behind the scenes injection point is a simple counter that gets decremented on
each iteration if parameter matches and crashes when counter reaches 0.

Q: Thank you very much for your detailed answers!
Wlad: You’re welcome.

Now back to our usual report: it is mid of April and our team is now focused on fixing
recovery bugs for the next two months.

Since my last report from 2009-04-03 we fixed around 11 Falcon related bugs.
Compared to our last WFTO from 2009-04-03 we have three new tests and we deleted
one obsolete test.

The development of our failed/passed tests ratio over time looks like:

  • 0.40% – 1/253 (this report)
  • 1.20% – 3/249 (last report)
  • 0.80% – 2/249 (report before last one)

weekly_falcon_test_overview_2009-04-17

News for this week:

  • Ann Harrison fixed
    • Bug#39130 Unbounded serial log growth with online ALTER
    • Bug#44096 Exception: Recovery failed: corrupted serial log
  • Kevin Lewis fixed
    • Bug#38568 Falcon assertion in Record::release – useCount > 0
    • Bug#42185 Falcon crashes during large transaction, assert(source->useCount >= 2)
    • Bug#44161 Falcon crashes in MemMgr::blockSize(data.record)
    • Bug#44224 Falcon crash in Table::fetchNext
    • Bug#44233 Crash in Table::validateAndInsert when updating cardinalities
  • Jim Starkey fixed
    • Bug#39890 Falcon Error: page 0/1 wrong page type, expected 7 got 1
  • Vladislav Vaintroub fixed
    • Bug#42208 Falcon’s ORDER BY ..LIMIT gives wrong/inconsistent results on NULL values
    • Bug#43765 falcon_bug_22173a crashes in IndexPage::findNodeInLeaf
    • Bug#44114 Falcon recovery Error: page 5342/1 wrong page type, expected 5 got 511

The failing test case is

  • falcon_bug_22154-big (305 out of record cache memory issue)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | Comments Off on WFTO – Weekly Falcon Test Overview 2009-04-17

WFTO – Weekly Falcon Test Overview 2009-04-03

WFTO – start of April report

it is start of April and we were very busy fixing bugs. Kevin, Jim,
and Olav implemented our new CycleManager, which closed a lot of bugs.

Olav implemented our new TransactionState object, which we also
account for closing quite a few bugs.

Since my last report from 2009-03-20 we fixed around 17 Falcon related bugs. Compared to our last WFTO from 2009-03-20 we have 1 new test.

The development of our failed/passed tests ratio over time looks like:

  • 1.20% – 3/249 (this report)
  • 0.80% – 2/249 (last report)
  • 2.51% – 6/239 (report before last one)

WFTO 2009-04-03

News for this week:

  • Christopher Powers fixed
  • John H. Embretsen fixed
    • Bug#43982 falcon_team test suite should be run in PB2 in specific falcon branches
  • Kelly Long fixed
    • Bug#43942 Make SyncObject::backoff really backoff
    • Bug#43995 Falcon Valgrind warnings in StorageInterface, StorageHandler & CmdGen
  • Kevin Lewis fixed
    • Bug#34624 Falcon: Slave contains one more record than master after a replication test
    • Bug#41742 Falcon REPEATABLE READ does not return repeatable results
    • Bug#42459 Falcon transactional consistency broken on WHERE IN( … )
    • Bug#43146 Falcon crash in EncodedDataStream::skip
    • Bug#43298 Falcon assertion record->recordNumber >= 0 in Transaction::addRecord
    • Bug#43299 Falcon crash in Record::addRef() – this=0xcccccccc00000000
  • Lars-Erik Bjørk fixed
    • Bug#40950 Falcon indexes broken for unsigned bigint
  • Olav Sandstaa fixed
    • Bug#41357 falcon.falcon_bug_34351_C fails with assertion IS_CONSISTENT_READ
    • Bug#41665 Falcon crash in Transaction::waitForTransaction
    • Bug#41850 Falcon reports 0 rows in table under concurrent workload
    • Bug#43858 falcon_limit crashes in Transaction::visible()
    • Bug#43958 Assertion (transState != NULL) failed in Transaction::waitForTransaction
  • Vladislav Vaintroub fixed
    • Bug#43562 Crash when creating a Falcon table after upgrade from 6.0.9 to 6.0.10

These are the three failing test cases.

  • falcon_bug_22972 (test case issue)
  • falcon_bug_24024 (test case issue)
  • falcon_deadlock (this was fixed but a new problem showed up: Bug#43554)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | Comments Off on WFTO – Weekly Falcon Test Overview 2009-04-03

WFTO – Weekly Falcon Test Overview 2009-03-20

WFTO – the March 2009 report!

We did a quite good job in February/March 2009 and fixed a lot of bugs.

Since my last report from 2009-02-06 we fixed around 39 Falcon related bugs. Compared to our last WFTO from 2009-02-06 we have 6 new tests.

The development of our failed/passed tests ratio over time looks like:

  • 0.80% – 2/249 (this report)
  • 2.51% – 6/239 (last report)
  • 1.69% – 4/237 (report before last one)

WFTO 2009-03-20

News for this week:

  • Christopher Powers fixed
    • Bug#28178 Falcon ALTER TABLE ends up in “Unknown table ‘sql-xyz’
    • Bug#32838 Falcon; error 1296 : Got error 305 ‘record memory is exhausted’
    • Bug#33177 Table creation fails after error 305 and tablespace change
    • Bug#36442 Falcon: crash during optimize table
    • Bug#38375 Falcon crash in Record::isNull
    • Bug#39445 Falcon: Update fails following online add column
    • Bug#39670 Error on rename (errno: 121) from ALTER TABLE ADD KEY in concurrent test
    • Bug#42592 Falcon assertion (insert(NULL, record, record->recordNumber)) when backlogging
    • Bug#42651 Regression: falcon_bug_22169-big started to fail with error 305
    • Bug#42725 Exception when filling I_S.TABLESPACES by Falcon (backup.backup_timeout failure)
    • Bug#42830 Falcon Exception: ResultSet has been closed after recovery
    • Bug#43504 Falcon DBT2 crash in Table::rollbackRecord()
  • Hakan Kuecuekyilmaz fixed
    • Bug#43182 Disabled falcon_unicode-big and falcon_blob_space-big
  • Kevin Lewis fixed
    • Bug#34182 SELECT … FOR UPDATE does not lock when in subquery
    • Bug#42340 Falcon assertion (oldestVisible->state != recLock) in RecordLeaf::pruneRecords
    • Bug#42660 Falcon bug in SparseArray.h
    • Bug#42828 Falcon crash in Table::checkUniqueRecordVersion – transaction = 0x0
    • Bug#43200 Falcon crash at startup in Database::scavenge()
  • Lars-Erik Bjørk fixed
    • Bug#23692 Falcon: searches fail if data is 0x00
    • Bug#33190 Falcon: DeferredIndex and IndexKey may sort slightly differently
    • Bug#33719 CREATE TABLE only accepts falcon_user tablespace in uppercase
    • Bug#34478 Falcon: search failure with varbinary = 0x00
    • Bug#38130 Falcon assertion in IndexNode::expandKey offset + length <= MAX_PHYSICAL_KEY_LEN
    • Bug#42341 Falcon assertion (key – (UCHAR*) indexNode < 14) in IndexNode::parseNode
    • Bug#43452 Wrong number of rows returned when using LIMIT
    • Bug#43488 Crash in Table::fetchForUpdate (update conflict) when using LIMIT query
  • Olav Sandstaa fixed
    • Bug#36410 Falcon crashes on 64 concurrent threads
    • Bug#40155 [Falcon] Error: assertion (ret == 0) failed at line 80 in file Mutex.cpp
    • Bug#40274 Falcon assertion in Transaction::releaseDependencies at Transaction.cpp:792
    • Bug#40633 pushbuild failure: Falcon assertion “lockState == 0” failed in SyncObject.cpp
    • Bug#42568 Falcon: Crash in SyncObject::unlock at line 976 in SyncObject.cpp
    • Bug#43048 Falcon may crash during shutdown when running it embedded
  • Vladislav Vaintroub fixed
    • Bug#35255 falcon_bug_22165.test fails with debug builds
    • Bug#41837 Falcon recovery error: page 102/0 wrong page type, expected 7 got 0
    • Bug#42745 Exception: can’t find table space during recovery
    • Bug#42344 Falcon recovery Exception: read error on page Invalid argument (22)
    • Bug#42478 Falcon crash in Database::updateSequence
    • Bug#42560 Falcon recovery error: page 411048/1 wrong page type, expected 5 got 7
    • Bug#42824 Falcon assertion (lockType == Exclusive) in Bdb::mark on REPAIR

These are the two failing test cases.

  • falcon_bug_22154-big
  • falcon_deadlock (this was fixed but a new problem showed up: Bug#43554)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | Comments Off on WFTO – Weekly Falcon Test Overview 2009-03-20

WFTO – Weekly Falcon Test Overview 2009-02-06

WFTO – recover or not?

Yes! This was again a bug fixing week. Vladislav Vaintroub fixed a lot of recovery related bugs and Kevin Lewis and Chris Powers took care about the new scavenger and backlogging.

Since my last report from 2009-01-30 we fixed around 9 Falcon related bugs. Compared to our last WFTO from 2009-01-30 we have 4 new tests.

The development of our failed/passed tests ratio over time looks like:

  • 2.51% – 6/239 (this report)
  • 1.69% – 4/237 (last report)
  • 1.69% – 4/236 (report before last one)

WFTO 2009-02-06

News for this week:

  • Christopher Powers fixed
    • Bug#36442 Falcon: crash during optimize table
    • Bug#40937 ASSERT(transaction->thawedRecords > 0) fails
    • Bug#42424 Serious performance degradation after new scavenger
    • Bug#42505 Falcon: Record backlogging not enabled by the Scavenger
    • Bug#42510 Falcon: Default memory parameters must be changed
  • Vladislav Vaintroub fixed
    • Bug#40946 assertion in PageInventoryPage::allocPage in recovery
    • Bug#42542 falcon_bug_28095 crashes in StorageHandler::dropTempTables
    • Bug#41227 Falcon: potential corruption of RecordLocatorPage on recovery
    • Bug#42227 Test falcon.falcon_bug_28095 fails sporadically on pushbuild

These are the three of the six failing test cases. I have to admit, that I cannot find the remaining three failures. Maybe we suffer from “Lost Update” or a “Phantom Read“?

  • falcon_bug_22169-big (new regression)
  • falcon_bug_30124-big
  • falcon_deadlock (a fix for this test failure is in review)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | 1 Comment

WFTO – Weekly Falcon Test Overview 2009-01-30

WFTO – end of January report

Yes! This was a bug fixing week

Since my last report from 2009-01-23 we fixed around 15 Falcon related bugs. Compared to our last WFTO from 2009-01-23 we have 1 new test.

The development of our failed/passed tests ratio over time looks like:

  • 1.69% – 4/237 (this report)
  • 1.69% – 4/236 (last report)
  • 1.28% – 3/234 (report before last one)

WFTO 2009-01-30

News for this week:

  • Christopher Powers fixed
    • Bug#39678 Assertion (bdb) fails in IndexRootPage::indexMerge during recovery
    • Bug#41663 Falcon assertion (deferredIndex->virtualOffset) failed at Index.cpp:264
    • Bug#42099 Falcon: Online ALTER add/drop primary key
    • Bug#42131 falcon_backlog test crashes in Record::getEncodedValue
    • Bug#42274 Running iuds6.tst leads to assertion in Falcon
    • Bug#42342 Falcon crash in Index::duplicateKey
  • Kevin Lewis fixed
    • Bug#40801 Falcon garbage collection can erase valid key values
    • Bug#42365 Double call defaultDatabase->getOpenConnection() in StorageHandler::initialize
    • Bug#42429 Falcon crash in Table::checkUniqueRecordVersion
  • Vladislav Vaintroub fixed
    • Bug#40946 assertion in PageInventoryPage::allocPage in recovery
    • Bug#41227 Falcon: potential corruption of RecordLocatorPage on recovery
    • Bug#42060 Falcon recovery failure – wrong page type, expected 8 got 0 (redoIndexPage)
    • Bug#42392 Falcon bugs in recovery of create tablespace
    • Bug#42394 Unnecessary calls to TableSpace::open() in TableSpaceManager::bootstrap()
    • Bug#42414 falcon_bug_33211 fails when trying to create a table in a non-existing table spa

The four failing test cases are:

  • falcon_bug_30124-big
  • falcon_bug_36294-big
  • falcon_deadlock (a fix for this test failure is in review)
  • falcon_bug_22173 (a fix for this regression will be merged into our Falcon source tree soon)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | Comments Off on WFTO – Weekly Falcon Test Overview 2009-01-30

Eat your own dogfood: extrem

Was heißt das?

Man soll sein eigenes Hundefutter essen? Nein, nicht ganz. Was gemeint ist, dass man sein hergestelltes Hundefutter seinem eigenen Hund füttert.

Die Idee wird sehr gerne in der Softwarebranche eingesetzt. Zum Beispiel die Versionsverwaltung von SVN in SVN betrieben und wir bei MySQL betreiben unsere Websites und internen Systeme immer mit der aktuellen Beta-Version unseres Datenbankservers.

In der Lebensmittelbranche wird gesagt, dass die Manager bei Aldi jeden Tag immer eine andere Teilmenge ihrer Produkte testen. Die Idee ist somit klar: man ist von seinem Produkt soweit überzeugt, dass man es auch selber nutzt.

Und nun eine ganz andere Branche: die Holzindustrie. Tagtäglich amputieren sich Menschen ihre Finger bei der Arbeit mit Tischkreissägen; in den meisten Fällen ohne echte Absicht, wenn man von den Legenden japanischer Untergrundorganisationen absieht.

Und nun in Extrem

Stephen Gass hat sich gesagt: “Das muss doch nicht sein”. Der Kreissäge müsste man doch beibringen können, ob es nun gerade Holz oder einen Finger trennt. Gesagt, getan und er hat es SawStop genannt. Wenn man Holz sägt, dann wird gesägt. und wenn ein Finger an das Sägeblatt kommt, dann stoppt das Ding halt.

Da so etwas schwer zu glauben ist, hat er es natürlich mit seinem eigenen Finger probiert!

Eine weitere Version dieses Prinzips ist unter anderem

  • Der Beweis, dass eine Blinddarmoperation auch mit lokaler Anästhesie durchführbar ist. Der Arzt hat sich dann halt mal selber operiert.

Referenzen:

Posted in Random | Tagged , | Comments Off on Eat your own dogfood: extrem

MySQL 6.0.9 Alpha has been released!

We have a new Alpha release for MySQL 6.x

MySQL 6.0.9-alpha, a new version of the MySQL database system has been released. The main page for MySQL 6.0 release is at

MySQL 6.0 includes two new storage engines: the transactional Falcon engine, and the crash-safe Maria engine.

If you are new to the Falcon storage engine and need more information, please read the Falcon Evaluation Guide at

and the Falcon White Paper at

The Maria storage engine is a crash safe version of MyISAM. Maria supports all of the main functionality of the MyISAM engine, but includes recovery support (in the event of a system crash), full logging (including CREATE, DROP, RENAME and TRUNCATE operations), all MyISAM row formats and a new Maria specific row format. Maria is documented at

MySQL 6.0.9-alpha is available in source and binary form for a number of platforms from our download pages at

and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can’t find this version on some mirror, please try again later or choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes, and patches at

The following section lists important, incompatible and security changes since the previous version of MySQL 6.0. The full changelog, including many more fixes can be viewed online at

What about you?

We are interested in you! Where do you use MySQL 6.x? What do you do with MySQL 6.x? Are there any features you want to see in our MySQL 6.x series? You can test MySQL 6.x and get famous by providing valuable bug reports and feature requests!

Posted in MySQL | Tagged , , , | 2 Comments

WFTO – Weekly Falcon Test Overview 2009-01-23

WFTO – a few more bug fixes

Our MySQL/Falcon team is back from vacation and we were very productive in fixing bugs. Last week Kevin pushed his new scavenger code and after a few bug fixes in the new scavenger code long outstanding memory leak issues were fixed.

Since my last report from 2009-01-16 we fixed around 7 Falcon related bugs. Compared to our last WFTO from 2009-01-16 we have 3 new test.

The development of our failed/passed tests ratio over time looks like:

  • 1.69% – 4/236(this report)
  • 1.28% – 3/234(last report)
  • 1.29% – 3/233 (report before last one)

WFTO 2009-01-23

News for this week:

  • Christopher Powers fixed
    • Bug#39678 Assertion (bdb) fails in IndexRootPage::indexMerge during recovery
    • Bug#41663 Falcon assertion (deferredIndex->virtualOffset) failed at Index.cpp:264
    • Bug#42131 falcon_backlog test crashes in Record::getEncodedValue
    • Bug#42274 Running iuds6.tst leads to assertion in Falcon
  • Lars-Erik Bjørk fixed
    • Bug#42196 Issue with key look up for bit field in Falcon table after insert + stored func
  • Sergey Vojtovich fixed
    • Bug#42079 Falcon does not reset auto_increment on transactional truncate
  • Vladislav Vaintroub fixed
    • Bug#42136 Falcon: odd behavior for range query on index prefix when MRR is disabled

The four failing test cases are:

  • falcon_bug_30124-big
  • falcon_bug_36294-big
  • falcon_deadlock (a fix for this test failure is in review)
  • falcon_bug_22173 (a fix for this regression will be merged into our Falcon source tree soon)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | Comments Off on WFTO – Weekly Falcon Test Overview 2009-01-23

WFTO – Weekly Falcon Test Overview 2009-01-16

WFTO – new scavenger and more bug fixes

Our MySQL/Falcon team is back from vacation and we were very productive in fixing bugs. Last week Kevin pushed his new scavenger code and after a few bug fixes in the new scavenger code long outstanding memory leak issues were fixed.

Since my last report from 2009-01-09 we fixed around 8 Falcon related bugs. Compared to our last WFTO from 2009-01-09 we have 1 new test.

The development of our failed/passed tests ratio over time looks like:

  • 1.28% – 3/234(this report)
  • 1.29% – 3/233 (last report)
  • 1.29% – 3/232 (report before last one)

WFTO 2009-01-16

News for this week:

  • Kevin Lewis fixed
    • Bug#36700 Running falcon_bug_28048 shows increasing memory usage and run time
    • Bug#41521 falcon_bug_34174 fails with lock wait timeout, sometimes
    • Bug#41831 Error: assertion (record->state != recLock) failed at line 1999 in file Table.cp
    • Bug#41870 Unbounded tablespace growth when updating BLOB record
    • Bug#42006 Running falcon_bug_22207-big on 32-bit Linux leads to crash
    • Bug#42080 falcon_record_cache_memory_leak2 crashes in RecordVersion::scavengeSavepoint
  • Olav Sandstaa fixed
    • Bug#37281 Time stamps in Falcon on big-endian machine give wrong results
  • Vladislav Vaintroub fixed
    • Bug#35255 falcon_bug_22165.test fails with debug builds

The three failing test cases are:

  • falcon_bug_30124-big
  • falcon_bug_36294-big
  • falcon_deadlock (a fix for this test failure is in review)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!

Resources:

Posted in MySQL | Tagged , , , , , , | 1 Comment