From: Reindl Harald
Date: January 28 2013 3:05pm
Subject: Re: log sequence number InnoDB: is in the future!?
List-Archive: http://lists.mysql.com/mysql/228883
Message-Id: <510693B8.90508@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="----enig2TIUJIWQMTXIDDBVNDDOA"

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



Am 28.01.2013 16:01, schrieb walter harms:
>=20
>=20
> Am 28.01.2013 14:40, schrieb Andrew Moore:
>> Dump and reload or use some scripting to create and drop some fake dat=
a to
>> increase the lsn towards the 'future' value.
>>
>> http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysq=
l-innodb-log-in-the-future
>>
>=20
> For now i tend to solution 3, rsync
> do you know is it possible only certain files?

no way

innodb has a global tablespace even with files_per_table


------enig2TIUJIWQMTXIDDBVNDDOA
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.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEGk7gACgkQhmBjz394AnlqOgCdE4C54TSuN+CRN6teB0tS6OB9
EZIAnRMSWGNje2x069uEFvMhZb96sXN4
=qmzh
-----END PGP SIGNATURE-----

------enig2TIUJIWQMTXIDDBVNDDOA--