Bug #48632 Fix for Bug #23300 Has Not Been Backported To 5.x Release
Submitted: 9 Nov 2009 9:38 Modified: 21 Jun 2010 0:52
Reporter: Andy Pritchard Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:All OS:Any
Assigned to: Luis Soares CPU Architecture:Any
Tags: Bug #23300, replication
Triage: Triaged: D3 (Medium) / R2 (Low) / E2 (Low)

[9 Nov 2009 9:38] Andy Pritchard
Description:
The fix for Bug #23300 was only pushed into MySQL 6.x which has since been retired. The slow log documentation still points to this bug which is now closed but essentially not fixed.
This fix should be ported to the 5.x generation.

How to repeat:
See http://dev.mysql.com/doc/refman/5.0/en/slow-query-log.html and the description of bug #23300 [ http://bugs.mysql.com/bug.php?id=23300 ]
[9 Nov 2009 12:13] Valeriy Kravchuk
I'll re-open bug #23300 and require backporting of the fix.
[23 Jan 2010 3:17] 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/97961

3333 Luis Soares	2010-01-23
      BUG#48632: Fix for Bug #23300 Has Not Been Backported 
      To 5.x Release
      
      Notes
      =====
      
      This is a backport of BUG#23300 into 5.1 GA.
      
      Original cset revid:
      luis.soares@sun.com-20090219085910-05i23vtboj9gj4fx
      
      Description
      ===========
      
      When using replication, the slave will not log any slow query
      logs queries replicated from the master, even if the
      option "--log-slow-slave-statements" is set and these take more
      than "log_query_time" to execute.
                    
      In order to log slow queries in replicated thread one needs to
      set the --log-slow-slave-statements, so that the SQL thread is
      initialized with the correct switch. Although setting this flag
      correctly configures the slave thread option to log slow queries,
      there is an issue with the condition that is used to check
      whether to log the slow query or not. When replaying binlog
      events the statement contains the SET TIMESTAMP clause which will
      force the slow logging condition check to fail. Consequently, the
      slow query logging will not take place.
                    
      This patch addresses this issue by removing the second condition
      from the log_slow_statements as it prevents slow queries to be
      binlogged and seems to be deprecated.
[25 Jan 2010 23:56] Omer Barnir
Bug#23300 was addressed in 5.5 and above, it cannot be back ported to 5.1 as in leads to a change in behavior that is not to be done in GA releases.
[26 Jan 2010 8:56] Andy Pritchard
Surely the change in behaviour is already there - that certain queries do not get logged to the slow-log.

This is causing me quite a headache because a very fast master server with relevant index blocks cached etc. has no problem running an update. 
Replication to older slower slaves on the other is not as fast and one or more of the updates is causing a go-slow between 0500-0630. I'm not aware of a way to track the update at fault.
[5 Feb 2010 17:01] 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/99494

3367 Luis Soares	2010-02-05
      BUG#48632: Fix for Bug #23300 Has Not Been Backported 
      To 5.x Release
            
      Notes
      =====
            
      This is a backport of BUG#23300 into 5.1 GA.
            
      Original cset revid (in betony):
      luis.soares@sun.com-20090929140901-s4kjtl3iiyy4ls2h
      
      Description
      ===========
            
      When using replication, the slave will not log any slow query
      logs queries replicated from the master, even if the
      option "--log-slow-slave-statements" is set and these take more
      than "log_query_time" to execute.
                          
      In order to log slow queries in replicated thread one needs to
      set the --log-slow-slave-statements, so that the SQL thread is
      initialized with the correct switch. Although setting this flag
      correctly configures the slave thread option to log slow queries,
      there is an issue with the condition that is used to check
      whether to log the slow query or not. When replaying binlog
      events the statement contains the SET TIMESTAMP clause which will
      force the slow logging condition check to fail. Consequently, the
      slow query logging will not take place.
                          
      This patch addresses this issue by removing the second condition
      from the log_slow_statements as it prevents slow queries to be
      binlogged and seems to be deprecated.
[1 Mar 2010 8:47] Bugs System
Pushed into 5.1.45 (revid:joro@sun.com-20100301083827-xnimmrjg6bh33o1o) (version source revid:joerg@mysql.com-20100212173307-ph563zr4wmoklgwd) (merge vers: 5.1.45) (pib:16)
[1 Mar 2010 13:12] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html
[1 Mar 2010 13:12] Jon Stephens
See BUG#23300 for changelog entry.
[2 Mar 2010 14:32] Bugs System
Pushed into 6.0.14-alpha (revid:alik@sun.com-20100302142746-u1gxdf5yk2bjrq3e) (version source revid:alik@sun.com-20100225090938-2j5ybqoau570mytu) (merge vers: 6.0.14-alpha) (pib:16)
[2 Mar 2010 14:37] Bugs System
Pushed into 5.5.3-m2 (revid:alik@sun.com-20100302072233-t3uqgjzdukt1pyhe) (version source revid:alexey.kopytov@sun.com-20100209075938-mmcnyf6w631ozc45) (merge vers: 5.5.2-m2) (pib:16)
[2 Mar 2010 14:42] Bugs System
Pushed into mysql-next-mr (revid:alik@sun.com-20100302072432-k8xvfkgcggkwgi94) (version source revid:alik@sun.com-20100224135227-rcqs9pe9b2in80pf) (pib:16)
[3 Mar 2010 4:50] Jon Stephens
Already documented in 5.5.0/6.0.11 changelogs. Re-closing.
[17 Jun 2010 12:20] Bugs System
Pushed into 5.1.47-ndb-7.0.16 (revid:martin.skold@mysql.com-20100617114014-bva0dy24yyd67697) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)
[17 Jun 2010 13:08] Bugs System
Pushed into 5.1.47-ndb-6.2.19 (revid:martin.skold@mysql.com-20100617115448-idrbic6gbki37h1c) (version source revid:martin.skold@mysql.com-20100609140708-52rvuyq4q500sxkq) (merge vers: 5.1.45-ndb-6.2.19) (pib:16)
[17 Jun 2010 13:48] Bugs System
Pushed into 5.1.47-ndb-6.3.35 (revid:martin.skold@mysql.com-20100617114611-61aqbb52j752y116) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)