Subject | Re: [firebird-support] Re: enumeration table question |
---|---|
Author | Ann W. Harrison |
Post date | 2006-09-12T15:25:19Z |
Stan wrote:
have conflicting requests for resources, so that each is waiting
for the other(s), and no one can move. If however, A is waiting
for B and B has gone to get coffee, lunch, or a life, that is not
a deadlock, and Firebird will just wait. Versions 2 adds a lock
timeout parameter to transactions that will return an error if
the wait exceeds the defined limit.
Regards,
Ann
>Firebird detects deadlocks - cases where two (or more) transactions
> BUT, often, Firebid cannod detect the deadlocks and all my clients
> are just blocking on the query. I waited about 10 minutes for them to
> unblock, they did not. Why does this happen?
>
have conflicting requests for resources, so that each is waiting
for the other(s), and no one can move. If however, A is waiting
for B and B has gone to get coffee, lunch, or a life, that is not
a deadlock, and Firebird will just wait. Versions 2 adds a lock
timeout parameter to transactions that will return an error if
the wait exceeds the defined limit.
Regards,
Ann