maria-discuss team mailing list archive

Thread
Date

Re: ALTER TABLE ENIGNE=InnoDB performance

To: "maria-discuss@xxxxxxxxxxxxxxxxxxx" <maria-discuss@xxxxxxxxxxxxxxxxxxx>
From: Conor Murphy <conor_mark_murphy@xxxxxxxxxxx>
Date: Fri, 12 Jan 2018 23:30:51 +0000
Accept-language: en-IE, en-US
In-reply-to: <CAJuX1hxqU+-j3B_JW0meLGOUWB0L0XrgRTrAkuXar+ek=q-O-Q@mail.gmail.com>
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99
Thread-index: AQHTiUnDTNCM7ZXTT0C9HmJMuXDwu6NujAkAgAJZJCI=
Thread-topic: [Maria-discuss] ALTER TABLE ENIGNE=InnoDB performance

Hi Marko,


Thanks for the info. I re-did the ALTER, running each statement sequentially. This time the statements completed in a timely manner and there wasn't any ERRORs recorded about the table statistics.


However, the whole exercise has reached a dead-end as we need to be able to replicate the database and as far as I can tell we need "ALTER TABLE t DISCARD PARTITION ALL TABLESPACE" which isn't available.


Regards,

Conor

Follow ups

Re: ALTER TABLE ENIGNE=InnoDB performance
From: Marko Mäkelä, 2018-01-17

References

ALTER TABLE ENIGNE=InnoDB performance
From: Conor Murphy, 2018-01-09
Re: ALTER TABLE ENIGNE=InnoDB performance
From: Marko Mäkelä, 2018-01-11