> Yes, it's big. All transactions older than this "oldest" are known to
> be committed. Firebird keeps the state of every transaction between
> the oldest and the next so it can tell if the transaction that created
> the record committed and the record is valid

Hi Ann,

Thanks for the detailed explanation ! Nice to receive message from the master :-)
It is a default Firebird installation, so that will be superserver.

> (Grumbles about autocommit suppressed). Autocommit doesn't insure that
> transactions are committed

Ann, I was wondering if there is anything you can do at the application level to ensure that transactions are really committed ?
I mean, if a system crashes, it's already too late to intervene. The application terminated already. But I guess that is why sweep is there. In case of crash, later on the sweep will do the cleanup ?

> Has the performance improved?

I'm still waiting for feedback from the customer, thanks for asking, I will inform !

Many thanks and best regards,
Nico



[Non-text portions of this message have been removed]