Multitable deadlocks can usually be avoided if transactions accessing the same tables
lock those tables in the same order, either through implicit or explicit locks. For
example, all application developers might follow the rule that when both a master and
detail table are updated, the master table is locked first and then the detail table. If
such rules are properly designed and then followed in all applications, deadlocks are
very unlikely to occur.
When you know you will require a sequence of locks for one transaction, consider
acquiring the most exclusive (least compatible) lock first.
避免死锁
1. 如果事务按相同的顺序对相同的表加锁(隐式或显式),通常都能避免多表死锁
2. 当预先知道一个事务内需要获取一系列的锁时 , 可以考虑先获取排他性最高的锁
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/10599713/viewspace-990927/ ，如需转载，请注明出处，否则将追究法律责任。
-
博文量740
-
访问量2002852
最新文章
- 人力&人手&人才&人物
- oracle树中prior的用法
- Using Supplied Packages to Manage Stored Outlines
- $ORACLE_HOMERDBMSADMIN目录下各SQL的含义
- PRODUCT_USER_PROFILE Table
- Backing Up Server Parameter Files with RMAN
- Backing Up Control Files with RMAN
- Backing Up Individual Tablespaces with RMAN
- Making Whole Database Backups with RMAN
- 目睹奥运火炬传递
