-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User facing option to optimize database tables #25967
Comments
database storage report > action > optimize table > select doctype ?? |
We can optimize both MyISAM and InnoDB tables. |
Yep, had pointed out specifically for MyISAM since the need came about because the storage doesn't get freed up. |
https://www.postgresql.org/docs/current/sql-vacuum.html We can have something like |
Btw OPTIMIZE basically rewrites entire table for InnoDB. Optimize call causes a lot of I/O on large tables. People will spam this everywhere without knowing costs of it. It's simple query, doesn't need any special API IMO. |
True. Can be just db.sql in that case, will work on it |
🎉 This issue has been resolved in version 15.25.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Example: delete rows from
Data Import Log
- storage doesn't get freed up until you runOPTIMIZE TABLE `tabData Import Log`;
The text was updated successfully, but these errors were encountered: