| 1 |
Database Maintenance Module
|
| 2 |
|
| 3 |
Author:
|
| 4 |
David Kent Norman
|
| 5 |
http://deekayen.net/
|
| 6 |
|
| 7 |
DESCRIPTION
|
| 8 |
-----------
|
| 9 |
Runs an optimization query on selected tables for your database.
|
| 10 |
This should probably NOT be used to optimize every table in your
|
| 11 |
Drupal installation.
|
| 12 |
|
| 13 |
Per PostgreSQL documentation's recommendation, this module does
|
| 14 |
not use the VACUUM FULL operation that locks the tables; this
|
| 15 |
module can operate in parallel with normal reading and writing
|
| 16 |
of PostgreSQL tables.
|
| 17 |
|
| 18 |
MySQL's OPTIMIZE query uses table locks.
|
| 19 |
http://drupal.org/node/91621 is an example
|
| 20 |
where the table locking during the OPTIMIZE procedure could
|
| 21 |
interfere with basic functionality of your site when using MySQL.
|
| 22 |
|
| 23 |
Keep it down to tables where there is lot of data movement like
|
| 24 |
accesslog, cache, sessions, and watchdog. It's probably better to
|
| 25 |
make a separate, more infrequent cron as part of your regular
|
| 26 |
server management if you want to optimize your node tables.
|
| 27 |
|
| 28 |
INSTALLATION
|
| 29 |
------------
|
| 30 |
See INSTALL.txt in this directory.
|
| 31 |
|
| 32 |
TODO
|
| 33 |
----
|
| 34 |
Some sort of backup dump saver/emailer/ftp/etc.
|
Parent Directory
| 
Revision Log
| 
Revision Graph