MySQL Forums
Forum List  »  InnoDB

Re: version locking details for update ... where ...
Posted by: Peter Brawley
Date: September 13, 2017 09:32PM

If, on a modest modern machine, you run, say, five simultaneous threads of a hundred such updates on one row, you'll get a rollback rate of maybe 40%; read committed vs repeatable read won't make much difference to that rate, but adding For Update to the Select will get rid of most of them. Still, you'll need to add code to retry the transaction when it fails or deadlocks.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: version locking details for update ... where ...
513
September 13, 2017 09:32PM


Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.