diff options
| author | Martin Trigaux <mat@openerp.com> | 2014-09-22 17:56:51 +0200 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2015-01-22 13:34:19 +0100 |
| commit | 9f8731ca27d23fbe271f7eaa8c580afa62fec0fb (patch) | |
| tree | 9a6db0f2fea8108ed063a776e7c7378364cbe837 /addons/analytic_user_function | |
| parent | d970cc40f8fb9aed0af7708cd121880e45ee219e (diff) | |
[FIX] base: backport of 152c5c2 to 7.0
[IMP] base: safer locking at user login
When a users connects, a lock is taken on the res_user table to modify the last login date. If another running transaction uses a foreign key to res.users (e.g. write_uid column), postgres may detect the update as a concurrent update and rollback the transaction.
In pg 9.3, the lock_strength parameter 'NO KEY' allows a weaker lock which is less likely to break another transaction.
Fixes #552
Diffstat (limited to 'addons/analytic_user_function')
0 files changed, 0 insertions, 0 deletions