Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Regular postgres VACUUM command

Archives

Contributors

Re: Regular postgres VACUUM command

Re: Regular postgres VACUUM command

Hi,

In general, auotvaccum is a postgres setting which does that. Usually, I thought it was enabled by default.

In terms of index choice and counts, that is also a postgres setting, default_statistics_target which is probably set too low.

Of course there are myriad other postgres settings which affect what the planner does.

There are some OCA/FOSS modules I have seen over the years for logging slow queries, creating indexes etc, I've never used, but if you really want to run specific commands in Odoo, then it is simple enough with a server action as you can just do env.cr.execute.

On Wed, Jul 26, 2023 at 6:52 AM tblauwendraat <notifications@odoo-community.org> wrote:
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?

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Graeme Gellatly - 11:01 - 25 Jul 2023

Reference

  • Regular postgres VACUUM command
    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?
    by Tom Blauwendraat - 08:51 - 25 Jul 2023