Please sign in to comment.
[FIX] base: fix ir.logging database locking when using --log-db
Before this patch, the ir.logging's write_uid field was a many2one which could cause a module install/update to hang when the module is changing the res.users model schema and when this module causes to orm to warn through the logger. (eg: declaring two res.users fields with the same string attribute) In such situation the transaction cursor that is processing the res_users table alteration will be granted an exclusive postgresql lock hence causing the ir_logging insertion to block because of the write_uid foreign key to res_users. This issue has never been raised by runbot as it is using a remote database with --log-db Note: the write_uid conversion from m2o to int was left over in commit e6a5d82 closes #32015 Signed-off-by: Christophe Simonis <email@example.com>
- Loading branch information...