Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Regular postgres VACUUM command
by
Therp, Tom Blauwendraat
Hello,
I'm faced with an Odoo database that is quite active and has some very big tables. I also notice that sometimes, indexes go unused and the query plans go haywire (30 secs where it could be 70ms if using a certain index)
I've learned that this could be because Postgres misestimates the size of the tables, and i should run ANALYZE on the table. VACUUM ANALYZE and other VACUUM commands can remedy this, when run regularly.
I would have expected some kind of OCA module that has scheduled actions for this, but I havent found any.
How would you / have you handle(d) this situation? Would a new OCA module be of use?
I'm faced with an Odoo database that is quite active and has some very big tables. I also notice that sometimes, indexes go unused and the query plans go haywire (30 secs where it could be 70ms if using a certain index)
I've learned that this could be because Postgres misestimates the size of the tables, and i should run ANALYZE on the table. VACUUM ANALYZE and other VACUUM commands can remedy this, when run regularly.
I would have expected some kind of OCA module that has scheduled actions for this, but I havent found any.
How would you / have you handle(d) this situation? Would a new OCA module be of use?
