List:General Discussion« Previous MessageNext Message »
From:Reindl Harald Date:January 28 2013 3:05pm
Subject:Re: log sequence number InnoDB: is in the future!?
View as plain text  

Am 28.01.2013 16:01, schrieb walter harms:
> 
> 
> Am 28.01.2013 14:40, schrieb Andrew Moore:
>> Dump and reload or use some scripting to create and drop some fake data to
>> increase the lsn towards the 'future' value.
>>
>>
> http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql-innodb-log-in-the-future
>>
> 
> 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


Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Thread
log sequence number InnoDB: is in the future!?walter harms28 Jan
  • Re: log sequence number InnoDB: is in the future!?Andrew Moore28 Jan
    • Re: log sequence number InnoDB: is in the future!?walter harms28 Jan
      • Re: log sequence number InnoDB: is in the future!?Reindl Harald28 Jan
  • Re: log sequence number InnoDB: is in the future!?Manuel Arostegui28 Jan
    • Re: log sequence number InnoDB: is in the future!?walter harms28 Jan
      • Re: log sequence number InnoDB: is in the future!?Andrew Moore28 Jan
        • Re: log sequence number InnoDB: is in the future!?walter harms29 Jan
  • Re: log sequence number InnoDB: is in the future!?Larry Martell2 Feb
    • Re: log sequence number InnoDB: is in the future!?walter harms3 Feb
      • Re: log sequence number InnoDB: is in the future!?Larry Martell3 Feb
        • Re: log sequence number InnoDB: is in the future!?Reindl Harald3 Feb
        • Re: log sequence number InnoDB: is in the future!?Manuel Arostegui4 Feb
          • RE: log sequence number InnoDB: is in the future!?Benjamin Stillman4 Feb