Re: 'commit' in slow query log?
From: Jerry Stuckle <jstucklex_at_attglobal.net>
Date: Tue, 14 Feb 2017 09:58:57 -0500
Message-ID: <o7v5rt$99b$1_at_jstuckle.eternal-september.org>
Date: Tue, 14 Feb 2017 09:58:57 -0500
Message-ID: <o7v5rt$99b$1_at_jstuckle.eternal-september.org>
On 2/14/2017 9:51 AM, lauri.jauhiainen_at_gmail.com wrote:
> On Friday, May 20, 2016 at 6:26:49 AM UTC+3, Jerry Stuckle wrote:
>> On 5/19/2016 10:45 PM, gb.oldgarey_at_gmail.com wrote: >>> On Wednesday, 24 December 2008 15:38:59 UTC+8, flycondor wrote: >>>> I found many 'commit' in my slow query log >>>> does anyone know what's matter? >>>> >>>> example : >>>> >>>> # Time: 081223 23:40:49 >>>> # User_at_Host: [user] @ appserver [192.168.1.5] >>>> # Query_time: 2 Lock_time: 0 Rows_sent: 0 Rows_examined: 0 >>>> commit; >>> >>> i m facing the same issue, anybody have idea? thx >>> >> >> The same problem as someone had over seven years ago? Unless you're >> running a very old version of MySQL, I highly doubt it. >> >> But if you are running that old of a version, you need to update it. >>
>
> No. Problem is that he just gets "COMMIT" in slow query log. You can see that there is big transaction going on, but you don't know what that transaction contained.
>
Maybe, maybe not. But my response stands. If he had the same problem as someone seven years ago, he's running a very old version of MySQL. If he's up to date on his version, it's not the same problem.
-- ================== Remove the "x" from my email address Jerry Stuckle jstucklex_at_attglobal.net ==================Received on Tue Feb 14 2017 - 15:58:57 CET