Closed (fixed)
Project:
DB Maintenance
Version:
5.x-1.2
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2008 at 14:46 UTC
Updated:
25 Jan 2008 at 16:52 UTC
Hi,
I wanted to know wether I can use this module on a production site? Refers http://drupal.org/node/91621
I'm testing with drupal 5.6 with
Apache/2.2.3 (Win32)
PHP/5.2.0
MySQL/5.0.27
using as prod site (until end of january) drupal 5.3 on MacOS X.5 Intel and MAMP Pro 1.7.1
Thank you. Greetings
A.R.
Comments
Comment #1
deekayen commentedI can't answer the question for you. As I said in the issue you linked to, "it depends." The OPTIMIZE query locks the tables in your database when it is processing the data. That could mean data loss if you have a huge table (hundreds of thousands of records) and your users are trying to write to something that's locked.
You need to understand the impacts of the OPTIMIZE query and use the module as a way to automate what you would have already been doing as part of regular maintenance. The system specs you provided have no impact on what decision you should make. Better things to look at are your low points of activity on your site, how many records you have in the tables you want to optimize, and whether or not you trust your backups, though OPTIMIZE is more likely to fix corruption than create it.
All that said, I use the modules on about 5 small production sites, including http://deekayen.net/, and have never had a problem related to it.
You have made me think the module should have the option to automatically turn maintenance mode on and off when it is working. http://drupal.org/node/208884
Comment #2
doc2@drupalfr.org commentedWow, thank you for your comment, no jokes, this is really helpful to me!
Comment #3
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.