Author: Cantu

Some fixes for known problems will be commited next week. After that it will be submitted to QA tests, so probably we will have RC3 released at end of June.

Several documents, including books, manuals, papers, tutorials, etc. says that Firebird will start the sweep of a database if the difference between OAT (Oldest Active Transaction) and OIT (Oldest Interesting Transaction) reaches the pre-defined value of sweep interval setting. Some docs, like the ones from InterBase 6.0, even states that the automated sweep will start when the difference between the Next Transaction and OIT reaches the sweep interval value.

So, this post intention is to to clarify what is the truth about automated sweep start, in the hope that people/authors around the world correct those documents to stop this confusion.

In a private talk with Vlad Khorsun, one of the core developers of the Firebird project, he confirmed that all the previous assumptions listed above are WRONG! Yep, it is not NT – OAT, and it is not OAT – OIT. The automated sweep will start if the difference between OST (Oldest Snapshot Transaction) and OIT is greater than the sweep interval defined. So, the correct formula is OST – OIT.

This is valid for all Firebird versions up to date. If you know any document or paper with the incorrect info, please notify the author so he can correct it.

Here is the piece of code that proves that:

if (trans->tra_oldest_active > dbb->dbb_oldest_snapshot)
 {
 dbb->dbb_oldest_snapshot = trans->tra_oldest_active;
...
 }

 // If the transaction block is getting out of hand, force a sweep

 if (dbb->dbb_sweep_interval &&
 !(tdbb->getAttachment()->att_flags & ATT_no_cleanup) &&
 (trans->tra_oldest_active - trans->tra_oldest > dbb->dbb_sweep_interval) &&
 oldest_state != tra_limbo)
 {
 // Why nobody checks the result? Changed the function to return nothing.
 start_sweeper(tdbb, dbb);
 }

The code is somewhat confusing, specially for people who is not used to Firebird code so, you must note that in the above code, tra_oldest_active represents the value of OST calculated at transaction start time. dbb_oldest_snapshot is cached value of OST, updated when any transaction starts. This may explain why so many docs are wrong… at a first look, tra_oldest_active may be interpreted as OAT, but it is not!