Percona Server moved to https://jira.percona.com/projects/PS

wrong value for log_slow_verbosity

Bug #691234 reported by Peter Zaitsev on 2010-12-16

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Percona Server moved to https://jira.percona.com/projects/PS	Fix Released	High	Oleg Tsarev

Bug Description

In 11.7

mysql> select @@log_slow_verbosity;
+----------------------+
| @@log_slow_verbosity |
+----------------------+
| microtime |
+----------------------+
1 row in set (0.00 sec)

This is when starting server with
log_slow_verbosity="full"

The log file in this case is reporting some strange mix:

# Time: 101216 19:08:01
# User@Host: root[root] @ localhost []
# Thread_id: 4 Schema: Last_errno: 0 Killed: 0
# Query_time: 50.000274 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0 Rows_read: 1
# Bytes_sent: 64 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
SET timestamp=1292526481;
select sleep(50);

It is not just standard mysql slow log format but it is not the full format (error code, innodb stats etc) either.

Related branches

lp:~percona-dev/percona-server/release-5.1.53-12-slow_extended-fix

Rejected for merging into lp:~percona-dev/percona-server/release-5.1.53

Alexey Kopytov (community): Disapprove on 2010-12-20

lp:~percona-dev/percona-server/5.1.54-2010_12_21-two-fix_bug_691234

Merged into lp:percona-server/release-5.1.54-12 at revision 179

Alexey Kopytov (community): Approve on 2010-12-22

lp:~percona-dev/percona-server/5.1.54-2010_12_21-one-test_improve

Merged into lp:percona-server/release-5.1.54-12 at revision 178

Alexey Kopytov (community): Approve on 2010-12-22

lp:percona-server/release-5.1.54-12

Vadim Tkachenko (vadim-tk) on 2010-12-16

Changed in percona-server:
assignee:	nobody → Oleg Tsarev (tsarev)
importance:	Undecided → High

Oleg Tsarev (tsarev) on 2010-12-16

Changed in percona-server:
status:	New → Confirmed

Revision history for this message

Peter Zaitsev (pz-percona) wrote on 2010-12-17: Re: [Bug 691234] Re: wrong value for log_slow_verbosity

Oleg,

Based on our conversation today as I understand it is actually 2 different
bugs (please feel free to fork it)

1) when use_global_long_query_time is entered on its own line in my.cnf it
is recognized as the second line for it is a parameter for it. It did not
allow such syntax (which I think is should as many boolean variables like
innodb_file_per_table). But what is worse it did not complain about the
incorrect option.

2) There is a problem with "microtime" reporting non standard things in slow
query log. The goal is for log time by default to be absolutely same as in
mysql 5.1 which would allow to use tools only supporting such log files with
Percona.

On Thu, Dec 16, 2010 at 11:45 AM, Oleg Tsarev <email address hidden>wrote:

> ** Changed in: percona-server
> Status: New => Confirmed
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/691234
>
> Title:
> wrong value for log_slow_verbosity
>
> Status in Percona Server with XtraDB:
> Confirmed
>
> Bug description:
> In 11.7
>
> mysql> select @@log_slow_verbosity;
> +----------------------+
> | @@log_slow_verbosity |
> +----------------------+
> | microtime |
> +----------------------+
> 1 row in set (0.00 sec)
>
>
>
> This is when starting server with
> log_slow_verbosity="full"
>
> The log file in this case is reporting some strange mix:
>
> # Time: 101216 19:08:01
> # User@Host: root[root] @ localhost []
> # Thread_id: 4 Schema: Last_errno: 0 Killed: 0
> # Query_time: 50.000274 Lock_time: 0.000000 Rows_sent: 1 Rows_examined:
> 0 Rows_affected: 0 Rows_read: 1
> # Bytes_sent: 64 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
> SET timestamp=1292526481;
> select sleep(50);
>
>
> It is not just standard mysql slow log format but it is not the full format
> (error code, innodb stats etc) either.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/percona-server/+bug/691234/+subscribe
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/

Oleg,

Based on our conversation today as I understand it is actually 2 different
bugs (please feel free to fork it)

1) when use_global_long_query_time  is entered on its own line in my.cnf it
is recognized as the second line for it is a parameter for it.  It did not
allow such syntax (which I think is should as many boolean variables like
innodb_file_per_table). But what is worse it did not complain about the
incorrect option.

2) There is a problem with "microtime" reporting non standard things in slow
query log.  The goal is for log time by default to be absolutely same as in
mysql 5.1 which would allow to use tools only supporting such log files with
Percona.

On Thu, Dec 16, 2010 at 11:45 AM, Oleg Tsarev <oleg.tsarev@percona.com>wrote:

> ** Changed in: percona-server
>       Status: New => Confirmed
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/691234
>
> Title:
>  wrong value for log_slow_verbosity
>
> Status in Percona Server with XtraDB:
>   Confirmed
>
> Bug description:
>  In 11.7
>
> mysql> select @@log_slow_verbosity;
> +----------------------+
> | @@log_slow_verbosity |
> +----------------------+
> | microtime            |
> +----------------------+
> 1 row in set (0.00 sec)
>
>
>
> This is when starting server with
> log_slow_verbosity="full"
>
> The log file in this case is reporting some strange mix:
>
> # Time: 101216 19:08:01
> # User@Host: root[root] @ localhost []
> # Thread_id: 4  Schema:   Last_errno: 0  Killed: 0
> # Query_time: 50.000274  Lock_time: 0.000000  Rows_sent: 1  Rows_examined:
> 0  Rows_affected: 0  Rows_read: 1
> # Bytes_sent: 64  Tmp_tables: 0  Tmp_disk_tables: 0  Tmp_table_sizes: 0
> SET timestamp=1292526481;
> select sleep(50);
>
>
> It is not just standard mysql slow log format but it is not the full format
>  (error code, innodb stats etc) either.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/percona-server/+bug/691234/+subscribe
>

-- 
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501   Skype:  peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/

Oleg Tsarev (tsarev) on 2010-12-17

Changed in percona-server:
status:	Confirmed → In Progress

Oleg Tsarev (tsarev) on 2010-12-22

Changed in percona-server:
status:	In Progress → Fix Committed

Ignacio Nin (ignacio-nin) on 2011-03-08

Changed in percona-server:
status:	Fix Committed → Fix Released

Revision history for this message

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-25:

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-451

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.