If you block user access during the recovery, would it be faster w/o the 
indexes and then add the indexes through alter table and then let the 
user's in. This is the recommended solution for recovery for DB2.  If you 
have to do a recovery, its normally assumed that the database is locked 
for single DBA use until its fully recovered.  This is how its done on 
the big systems.  Just a thought.


On Tue, 13 Mar 2001, Peter Zaitsev wrote:

> Date: Tue, 13 Mar 2001 11:43:30 +0300
> From: Peter Zaitsev <[EMAIL PROTECTED]>
> To: Heikki Tuuri <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re[2]: Innobase in MySQL
> 
> Hello Heikki,
> 
> Tuesday, March 13, 2001, 1:31:04 AM, you wrote:
> 
> HT> Joshua,
> 
> >>I hope you can also use MySQL dump, in which case, you don't have to shut 
> >>down, right?
> 
> HT> yes, you can use mysqldump without shutting down. It did not come to my
> HT> mind that actually mysqldump is a kind of online backup mechanism :).
> HT> Since Innobase is multiversioned, you will get consistent snapshots of
> HT> your tables, and since the consistent read does not set any locks, your
> HT> users should be able to update the tables concurrently. Here I have
> HT> to check if mysqldump sets a full table read lock on the table you dump:
> HT> for Innobase that is not needed, but maybe MySQL currently does this because of
> HT> other table types.
> 
> Well guys mysqldump have one serious problem - the speed.
> 
> The backup speed is quite upsetting and loads system much, but the
> worst thing is recovery speed.
> In my case the data is added in realtime - most queries are inserts
> which utilize system quite hard. So to recover data I have gathered
> for a month it will take about 1 week to feed mysql with mysqldump
> output, even with extended inserts. So at least this is not complete
> solution.
> 
> 
> -- 
> Best regards,
>  Peter                            mailto:[EMAIL PROTECTED]
> 
> 
> 
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> 

Sincerely,

William Mussatto, Senior Systems Engineer
CyberStrategies, Inc
ph. 909-920-9154 ext. 27


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to