![]() If so, the second updater proceeds with its operation using the updated version of the row. The search condition of the command (the WHERE clause) is re-evaluated to see if the updated version of the row still matches the search condition. If the first updater commits, the second updater will ignore the row if the first updater deleted it, otherwise it will attempt to apply its operation to the updated version of the row. ![]() If the first updater rolls back, then its effects are negated and the second updater can proceed with updating the originally found row. In this case, the would-be updater will wait for the first updating transaction to commit or roll back (if it is still in progress). However, such a target row might have already been updated (or deleted or locked) by another concurrent transaction by the time it is found. UPDATE, DELETE, SELECT FOR UPDATE, and SELECT FOR SHARE commands behave the same as SELECT in terms of searching for target rows: they will only find target rows that were committed as of the command start time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |