On Mon, Sep 16, 2019 at 5:48 PM Reindl Harald wrote:
> Am 16.09.19 um 16:43 schrieb Marko Mäkelä:
> > Ultimately, for new DDL statements, this should be fixed when
> > MDEV-17567 implements Atomic DDL. I do not think that we can even then
> > safely remove #sql2 tables from old installations,
Am 16.09.19 um 16:43 schrieb Marko Mäkelä:
>> it's a shame that you simply can't get rid of garbage from the global
>> tablespace
>
> Starting with MDEV-14585 InnoDB actually does drop #sql- tables during
> startup. The #sql2 tables are intentionally preserved, because during
> ALTER
On Mon, Sep 16, 2019 at 5:26 PM Reindl Harald wrote:
> Am 16.09.19 um 15:58 schrieb Sergei Golubchik:
> > It looks like the only way to get rid of this warning would be to drop
> > this table manually. Like, `create table t1 ... engine=innodb`
> > then copy t1.idb and t1.frm to #sql2-704-271.*
Am 16.09.19 um 15:58 schrieb Sergei Golubchik:
> Hi, Reindl!
>
> On Sep 14, Reindl Harald wrote:
>> Am 14.09.19 um 14:05 schrieb Sergei Golubchik:
>>> Hi, Reindl!
>>>
>>> 1. Do you actually have /dbmail/*271* files ?
>>
>> no as you can see "Cannot open datafile for read-only:
>>
Hi, Reindl!
On Sep 14, Reindl Harald wrote:
> Am 14.09.19 um 14:05 schrieb Sergei Golubchik:
> > Hi, Reindl!
> >
> > 1. Do you actually have /dbmail/*271* files ?
>
> no as you can see "Cannot open datafile for read-only:
> './dbmail/#sql2-704-271.ibd'", i deleted the temp files 10 years ago
>
5 matches
Mail list logo
