Subject RE: [firebird-support] Firebird.log
Author Henner Kollmann
> * Another is real deadlock, caused by two (or more) transactions
> that update data in some "unfortunate" order.
> Firebird will detect such situation and kill one of the statements
> that were waiting.
> Nothing is written in firebird.log.
Could you describe what's happening to get this sort of deadlock?
I sometimes have problems with a locked transaction.