Subject | Re: [firebird-support] Deadlock Simplified |
---|---|
Author | Ann W. Harrison |
Post date | 2006-11-17T17:12:12Z |
Stephen Davey wrote:
Single user applications never deadlock.
Multi-user applications never deadlock unless they
update or delete records.
Multi-user applications that do updates and deletes
won't deadlock if the updates and delete transactions
are serialized with something like a mutex that
allows only one to be active at any one time.
More practically, keep transactions that do updates and
deletes as short as possible, remembering that updates
and deletes done by triggers also count.
produced by the server.
Regards,
Ann
> Is there a quick and simple solution to deadlocks ?Well, Here are some less than practical suggestions...
Single user applications never deadlock.
Multi-user applications never deadlock unless they
update or delete records.
Multi-user applications that do updates and deletes
won't deadlock if the updates and delete transactions
are serialized with something like a mutex that
allows only one to be active at any one time.
More practically, keep transactions that do updates and
deletes as short as possible, remembering that updates
and deletes done by triggers also count.
> Is the classic server less likely than superserver to encounter issues ?No. Deadlocks are created by application logic and aren't (in theory)
produced by the server.
Regards,
Ann