- Mailing Lists
- Contributors
- Re: Regular postgres VACUUM command
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Regular postgres VACUUM command
> can anyone recommend a visual Postgres monitoring tool
I use pgbadger too but PGHero is my favorite tool to see real time stats
El vie, 28 jul 2023 a las 3:22, Tom Blauwendraat (<notifications@odoo-community.org>) escribió:
Thanks Moises and Graeme for the detailed information! I'm going to look at tweaking autovacuum and statistics settings for the busy tables. Also, whenever replacing a big chunk of data, I'll run ANALYSE <table> afterwards. As for most situations the default Postgres settings are fine, and I can't think of any "generic" solutions other than monitoring and doing individual tweaks, I won't create an OCA module for it. Parting question: can anyone recommend a visual Postgres monitoring tool that could ideally also work on Amazon RDS? I'm familiar with log parsing tools such as pgBadger, but maybe there's a tool out there somewhere that can give information just by connecting to the instance and running smart queries? -Tom_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Moisés López Calderón
Mobile: (+521) 477-752-22-30
Twitter: @moylop260
Twitter: @vauxoo
by Moisés López Calderón - 12:26 - 2 Aug 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