From: Rich Prohaska Date: September 12 2012 2:51pm Subject: Re: Schema inconsistency after inplace alter table in MySQL 5.6.6-m9 List-Archive: http://lists.mysql.com/internals/38585 Message-Id: MIME-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hello How does one recover from crashes that occur when altering a partitioned tab= le, especially if the operation is committed on the storage engine but the f= rm is old? Rich Prohaska On Sep 12, 2012, at 3:41 AM, Dmitry Lenev wrote: > Hello Rich! >=20 > * Rich Prohaska [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? >=20 > 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. >=20 > So the problem is not really something new and was there almost > forever. >=20 > We have already bugs reported about this and similar issues > (for example, see http://bugs.mysql.com/bug.php?id=3D25922). > 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. >=20 > Best regards, > Dmitry >=20 > --=20 > Dmitry Lenev, Software Developer > Oracle Development SPB/MySQL, www.mysql.com >=20 > Are you MySQL certified? http://www.mysql.com/certification >=20 > --=20 > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe: http://lists.mysql.com/internals >=20