Skip navigation links

MySQL Forums :: Newbie :: Deleted table file behavior!


Advanced Search

Re: Deleted table file behavior!
Posted by: Phillip Ward ()
Date: May 03, 2012 06:28AM

Any changes you make to data are first made in memory, then written to the binary log file and finally (indeed, eventually) to the data file(s).
I suspect what you're seeing is a change still "in flight".
The second change, made while the data file is unavailable, is made to an in-memory data block and to the binary log file but can't been written to the [missing] data file; this is perfectly acceptable, normal behaviour for MySQL.

After the restart, MySQL tries to sort this "mess", that is:
* what's in the data files,
* what's written to the binary log but not yet applied to the data file(s), and
* what's written to the binary log but that shouldn't be applied (i.e., uncommited changes).
As part of this, it notes the "reappearence" of your data file and applies the necessary changes - your new record - into the data file.

All that said, ripping bits of out of any DBMS while it's running is a seriously Bad Idea! 8-0

Regards, Phill W.

Options: ReplyQuote


Subject Written By Posted
Deleted table file behavior! Eliezer Figueroa 05/01/2012 11:12PM
Re: Deleted table file behavior! Barry Galbraith 05/02/2012 05:57PM
Re: Deleted table file behavior! Eliezer Figueroa 05/02/2012 10:19PM
Re: Deleted table file behavior! Barry Galbraith 05/02/2012 10:52PM
Re: Deleted table file behavior! Phillip Ward 05/03/2012 06:28AM
Re: Deleted table file behavior! Eliezer Figueroa 05/03/2012 12:44PM
Re: Deleted table file behavior! Rick James 05/05/2012 01:30PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.