Bug #54275 useless partitioning error messages written to error log

• Submitted: 7 Jun 2010 8:01
• Modified: 7 Jun 2010 8:04
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Verified
• Category: MySQL Server: Partitions
• Severity: S4 (Feature request)
• Version: 5.1.47, 5.5.3
• OS: Any
• CPU Architecture: Any

[7 Jun 2010 8:01] Shane Bester

Description:
today I found these in the error logs:

[ERROR] Failed to execute action for entry = 8 from ddl log
[ERROR] Failed to execute action for entry = 14 from ddl log
[ERROR] Failed to execute action for entry = 13 from ddl log
[ERROR] Failed to execute action for entry = 6 from ddl log
[ERROR] Failed to execute action for entry = 4 from ddl log
[ERROR] Failed to execute action for entry = 2 from ddl log

errors with no context are quite useless, especially if dba doesn't know
exactly what sql is being run by the users.

How to repeat:
read the logs. i can provide the original sql statements, if needed.  but for this feature request, the sql is not needed.

Suggested fix:
write the table name for the failed operation, or even better
write the original sql statement that caused this error.
thread id or username could be useful too (in all such contextless errors!)

the above could be done in debug builds only, if release builds are off limits...

[7 Jun 2010 8:04] MySQL Verification Team

to give some context, the error was seen on windows platform, and most likely due to using some strange table names with alter table .. partition by .. statements.
an example: alter table `šn«` add partition partitions 4

[9 Jun 2010 23:15] Mattias Jonsson

related to bug#53676 and bug#53770, ddl_log bugs.

[9 Jun 2010 23:17] Mattias Jonsson

Is it possible to get a copy of the ddl_log.log file in the data-directory (and a listing of the data directory too, like 'ls -R')?
It would help to investigate this further.

[11 Jun 2010 15:07] MySQL Verification Team

import this file on windows server to repeat error message

Attachment: tmp.sql (application/octet-stream, text), 184 bytes.

[11 Jun 2010 15:16] MySQL Verification Team

all the logs!

Attachment: ddllog_dbug_trace_errlog.rar (application/octet-stream, text), 61.57 KiB.