From: Reindl Harald
Date: November 4 2011 10:22pm
Subject: Re: InnoDB #sql files
List-Archive: http://lists.mysql.com/mysql/226243
Message-Id: <4EB465BC.1030901@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig9ADA56E877FA73501D0A9163"

--------------enig9ADA56E877FA73501D0A9163
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 04.11.2011 19:12, schrieb Ian Rubado:
> Hi there,
>=20
> I had the same issue as you posted about at the bottom of:
>=20
> http://bugs.mysql.com/bug.php?id=3D20867
>=20
> I was curious if you ever found a solution. I ended up converting table=
s to
> MyIsam and flushing my innodb files to resolve.

no, this bullshit files are staying here since summer 2009 and converting=

a production dbmail-database to myisam would be the same as destroy it


--------------enig9ADA56E877FA73501D0A9163
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk60ZbwACgkQhmBjz394AnkdrACgg35ipymYRyvLC9miwAm+AuQg
C9YAoJD0lTMhX78l7WFzb5TmqarpPuNS
=99lY
-----END PGP SIGNATURE-----

--------------enig9ADA56E877FA73501D0A9163--