problem with "vacuum full " of a db when openerp-server running
Bug #375361 reported by
Galtys
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Hello,
In ir_cron.py, when there are no cron jobs to process, cr.commit() is not being called, only cr.close(). This will return the connection to the connection pool but it will remain in "idle in transaction" state as it is not commited.
According to postgres 8.3 documentation, cr.execute('select * from ir_cron where ... will create a AccessShareLock on ir_cron, (as any select would). This preserves "vacuum full" to succeed as it requires a ExclusiveLock on all tables.
I haven't noticed this behaviour in the previous release (4.2)
Running "vacuum full" might not seem critical but connections should not remain "idle in transaction" for a longer time.
This bug is related to https:/
Related branches
Revision history for this message
| Fabien (Open ERP) (fp-tinyerp) wrote | #1 |
| Changed in openobject-server: | |
| status: | New → Fix Released |
To post a comment you must log in.
fixed in branch/5. Thanks, that's a good bug report.