Bug #14157 utf8 encoding in binlog without set character_set_client: e.g DROP temporary
Submitted: 19 Oct 2005 22:37 Modified: 5 Jun 2006 21:48
Reporter: Alexander Kirillov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.1.14/5.0.XX BK source OS:Linux (Linux)
Assigned to: Andrei Elkin CPU Architecture:Any

[19 Oct 2005 22:37] Alexander Kirillov 
Description:
koi8r names in USE and server-generated DROP /*!40005 TEMPORARY */ TABLE IF EXISTS statements in binary logs show up utf8 encoded despite explicit SET NAMES koi8r; client request. I mark this bug critical as it's screwing up my replicating slaves.

How to repeat:
# mysql -p
mysql> SET NAMES koi8r;
mysql> USE `koi8r name`;
mysql> CREATE TEMPORARY TABLE `koi8r name`
mysql> exit
# mysql -p
mysql> SET NAMES koi8r;
mysql> SHOW BINLOG EVENTS IN 'xxxxxx-bin.xxxxxx';

Note: both database and table names show up utf8 encoded in
DROP /*!40005 TEMPORARY */ TABLE IF EXISTS statement
[27 Oct 2005 17:59] Alexander Kirillov 
Probably it's not related to my replication problems.
Still the log should be readable if the client encoding is utf-8.
[24 Apr 2006 10:01] Andrei Elkin 
The title is changed to hint rather transparently what to do.
[25 Apr 2006 19:16] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/5504
[9 May 2006 20:02] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6167
[13 May 2006 9:42] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6337
[14 May 2006 17:09] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6359
[15 May 2006 16:12] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6390
[16 May 2006 13:50] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6465
[28 May 2006 16:47] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6941
[31 May 2006 10:51] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/7082
[31 May 2006 17:53] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/7107
[3 Jun 2006 19:46] Andrei Elkin 
fixed in 4.1.21 5.0.23 5.1.12
[5 Jun 2006 21:48] Mike Hillyer 
Documented in changelog:

  <listitem>
        <para>
          Binary log lacked character set information for table name
          when dropping temporary tables. (Bug #14157)
        </para>
      </listitem>