All,
In thinking about Yi Lu's imminent problem with the Firebird transaction number
size, I am wondering if as developers we have overlooked the reasonableness
of the situation (actually the lack thereof).
Reality: a simple backup / restore cycle is all that needs to be performed to
resolve
Just throwing another thing: Isn't some form of journaling expected to
appear in Firebird, as I've heard in the past?
If yes, the journal could be used to consolidade old transaction in one
and implement the thing about adjusting the transaction number and
making it overlap as I said
Actually, the telecom standard is 99.999% uptime which is referred to
as a Five-Nines system and we have had this for over a decade with
Firebird, running 24/7/365.
Our transaction count is quite high, if you consider the number of
databases being queried in parallel to perform the various tasks,
