Subject | Re: [Firebird-Architect] Read Committed No Wait transactions |
---|---|
Author | Ann W. Harrison |
Post date | 2004-09-27T14:00:14Z |
At 03:19 AM 9/24/2004, Pavel Cisar wrote:
hits another's error and rolls back. While it is hitting the error,
transmitting, processing, and issuing the rollback, the other transaction
hits some error and does the same. So the delete never happens, though
it is tried over and over.
Regards,
Ann
>Yes, definitely when the reaction to the collision is an instant retry.The problem with live-lock is that nothing gets done. One transaction
>But it's a problem only in specific scenario. When row was deleted, then
>there is nothing you can retry.
hits another's error and rolls back. While it is hitting the error,
transmitting, processing, and issuing the rollback, the other transaction
hits some error and does the same. So the delete never happens, though
it is tried over and over.
Regards,
Ann