How does one recover from crashes that occur when altering a partitioned table, especially
if the operation is committed on the storage engine but the frm is old?
On Sep 12, 2012, at 3:41 AM, Dmitry Lenev <Dmitry.Lenev@stripped> wrote:
> Hello Rich!
> * Rich Prohaska <prohaska@stripped> [12/09/09 00:48]:
>> The problem with inplace alter table operations isthat the rename of
>> the FRM schema is not transactional. Are there any plans to address
> This not only problem with in-place operations in 5.6, it is
> also present in 5.1/5.5 and also exists in some form for ALTER TABLE
> executed through creation and copying data to temporary table.
> So the problem is not really something new and was there almost
> We have already bugs reported about this and similar issues
> (for example, see http://bugs.mysql.com/bug.php?id=25922).
> But since this is pre-existing problem, which doesn't happen often,
> and fixing it requires fairly big changes to ALTER TABLE/other DDL
> it is unlikely that this will happen in 5.6 timeframe.
> Best regards,
> Dmitry Lenev, Software Developer
> Oracle Development SPB/MySQL, www.mysql.com
> Are you MySQL certified? http://www.mysql.com/certification
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: http://lists.mysql.com/internals