El 27/09/2012, a las 17:08, Ann Harrison <aharri...@ibphoenix.com> escribió: > > Page type 5 is a data page. What you ran into was an internal deadlock > that was recognized and your process lost. The problem was entirely in > memory, so no, I wouldn't worry about datbase corruption. In theory, > Firebird should never have an internal deadlock. You've just seen a > difference between theory and practice. As processors get faster and loads > get heavier, more cases that were overlooked previously turn out to be > possible in fact. Without a repeatable test or a core dump, these problems > are very hard to diagnose. So if it happens once, chalk it up to bad luck. > If it happens repeatedly, be prepared to work with the core developers. > > Good luck, > > Ann > I have observed this behaviour in firebird 2.5.2, when query monitoring tables with a heavy load.
Don't know if this is the case, but if it is, there is a way to look for. Jesus > [Non-text portions of this message have been removed]
