having the hability to stop the extra engines is a good candidate to go to
the todo list.
Stopping the server to do a reliable backup is not good solution...
The ideal would be a mysql command that read locks all innodb tables, then
we can backup the data file and the log files safely... Something that
would suspend the update of the data and log files, saving all queries in
memory until an unlock command is executed...
Is this possible, or there is a design limitation to do this? I never looked
into mysql source before, but if time permits we can always help...
Thanks
- Original Message -
From: Paul DuBois [EMAIL PROTECTED]
To: Gustavo A. Baratto [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, July 09, 2003 11:31 PM
Subject: Re: stopping innodb engine
At 21:47 + 7/9/03, Gustavo A. Baratto wrote:
Greetings,
What happens if I use the command below when innodb engine is running?
set global have_innodb=0;
You can easily find out by trying it. (Go ahead, nothing bad will
happen.)
I want to stop innodb engine without stopping the whole server for
backup (most tables are myisam).
Any ideas on how to do that?
You can't. Storage engines like InnoDB or BDB can only be disabled or
enabled at startup time. have_innodb and have_bdb are indicators
of the availability of these engines; they cannot be set while the
server is running.
Thank all
--
Paul DuBois, Senior Technical Writer
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
Are you MySQL certified? http://www.mysql.com/certification/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
