You are here

Home » API reference » DB Maintenance 5.2

README.txt in DB Maintenance 5.2

Same filename and directory in other branches
  1. 5 README.txt
  2. 6.2 README.txt
  3. 6 README.txt
  4. 7.2 README.txt
  5. 7 README.txt
Database Maintenance Module

Author:
David Kent Norman
http://deekayen.net/

DESCRIPTION
-----------
Runs an OPTIMIZE TABLE query on selected tables for MySQL.
This should probably NOT be used to optimize every table in your
Drupal installation. http://drupal.org/node/91621 is an example
where the table locking during the OPTIMIZE procedure could
interfere with basic functionality of your site. Keep it down
to tables where there is lot of data movement like accesslog,
history, or watchdog. It's probably better to make a separate,
more infrequent cron as part of your regular server management
if you want to optimize your node tables.

DEPENDENCIES
------------
MySQL

INSTALLATION
------------
See INSTALL.txt in this directory.

MORE INFORMATION
----------------
This module is by no means intended to be only for MySQL forever.
If PostgreSQL has an OPTIMIZE TABLE equivalent, it should on the
TODO list for this module.

Other possible TODO list items include some sort of backup dump
saver/emailer/ftp/etc and an option to not execute on EVERY cron run

File

README.txt
View source 
  1. Database Maintenance Module

  2. 

  3. Author:

  4. David Kent Norman

  5. http://deekayen.net/

  6. 

  7. DESCRIPTION

  8. -----------

  9. Runs an OPTIMIZE TABLE query on selected tables for MySQL.

  10. This should probably NOT be used to optimize every table in your

  11. Drupal installation. http://drupal.org/node/91621 is an example

  12. where the table locking during the OPTIMIZE procedure could

  13. interfere with basic functionality of your site. Keep it down

  14. to tables where there is lot of data movement like accesslog,

  15. history, or watchdog. It's probably better to make a separate,

  16. more infrequent cron as part of your regular server management

  17. if you want to optimize your node tables.

  18. 

  19. DEPENDENCIES

  20. ------------

  21. MySQL

  22. 

  23. INSTALLATION

  24. ------------

  25. See INSTALL.txt in this directory.

  26. 

  27. MORE INFORMATION

  28. ----------------

  29. This module is by no means intended to be only for MySQL forever.

  30. If PostgreSQL has an OPTIMIZE TABLE equivalent, it should on the

  31. TODO list for this module.

  32. 

  33. Other possible TODO list items include some sort of backup dump

  34. saver/emailer/ftp/etc and an option to not execute on EVERY cron run