[MDEV-4901] Drop temporary table generating warning message Created: 2013-08-15  Updated: 2013-09-07  Resolved: 2013-09-07

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.3
Fix Version/s: 10.0.4

Type: Bug Priority: Minor
Reporter: Daisy Yan Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux pa1-lda-001.dev.tradingscreen.com 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux

Attachments: File pa1-lda-001.dev.tradingscreen.com.3108.cnf     Text File reporting_3108_error.log    

 Description   

After a temp table is created

mysql 23:45:02 [PA DEV 001] [tempdb] [3108]> create temporary table x ( a int);
 
Query OK, 0 rows affected (0.04 sec)

Dropping it like this

mysql 23:45:14 [PA DEV 001] [tempdb] [3108]> drop table x;
 
Query OK, 0 rows affected (0.00 sec)

seems to generate a warning message in the log

InnoDB: We removed now the InnoDB internal data dictionary entry
 
InnoDB: of table 130814 23:44:43 [Warning] Invalid (old?) table or database name '#sql577f_15c2_0'
 
`mysql_tmp`.<result 2 when explaining filename '#sql577f_15c2_0'>.



 Comments   
Comment by Elena Stepanova [ 2013-08-15 ]

Hi,

Do you mean that it happens every time when you create/drop a temporary table?
Please attach your cnf file(s) and the whole error log from the server start.

Thanks.

Comment by Daisy Yan [ 2013-08-15 ]

Elena,

Yes every time a temporary table is dropped. I've attached the files.

Thanks.

Daisy

Comment by Daisy Yan [ 2013-09-07 ]

Is there any progress on this one? Thanks.

Comment by Elena Stepanova [ 2013-09-07 ]

Hi,

Is it still reproducible on 10.0.4? There have been a lot of changes and bugfixes, including InnoDB-related, in that version, it might have fixed the problem you were experiencing.

Comment by Daisy Yan [ 2013-09-07 ]

Oh I just tested on 10.0.4 and it's gone. Looks like it's fixed in this version. Thanks!

Comment by Elena Stepanova [ 2013-09-07 ]

Great!

Generated at Thu Feb 08 07:00:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.