long_query_time documentation needs to be updated
Bug #978686 reported by
Frederic Descamps
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Low
|
Hrvoje Matijakovic | ||
5.1 |
Fix Released
|
Low
|
Hrvoje Matijakovic | ||
5.5 |
Fix Released
|
Low
|
Hrvoje Matijakovic |
Bug Description
In the current documentation, for long_query_time it states that :
"If the value is set to 0, then all queries are logged. This is different from the standard MySQL build, where a value of 0 disables logging."
But it seems that since 5.1.21, the minimum is 0 and this doesn't disable the logging.
http://
Related branches
lp:~hrvojem/percona-server/bug997469-5.1
- Alexey Kopytov (community): Approve
-
Diff: 126 lines (+19/-29)6 files modifieddoc/source/diagnostics/innodb_stats.rst (+2/-3)
doc/source/diagnostics/mysql_syslog.rst (+1/-1)
doc/source/diagnostics/slow_extended.rst (+2/-2)
doc/source/installation/apt_repo.rst (+12/-0)
doc/source/reliability/innodb_corrupt_table_action.rst (+0/-23)
doc/source/scalability/innodb_extra_rseg.rst (+2/-0)
lp:~hrvojem/percona-server/bug792351-5.5
- Laurynas Biveinis (community): Approve
-
Diff: 203 lines (+42/-31)9 files modifieddoc/source/diagnostics/innodb_stats.rst (+1/-4)
doc/source/diagnostics/slow_extended_55.rst (+2/-3)
doc/source/flexibility/buff_read_ahead_area.rst (+1/-1)
doc/source/management/innodb_expand_import.rst (+1/-1)
doc/source/management/udf_maatkit.rst (+16/-17)
doc/source/reliability/innodb_recovery_update_relay_log.rst (+2/-2)
doc/source/scalability/innodb_expand_undo_slots.rst (+2/-2)
doc/source/scalability/innodb_io_55.rst (+14/-1)
doc/source/upgrading_guide_51_55.rst (+3/-0)
Changed in percona-server: | |
status: | New → Confirmed |
assignee: | nobody → Hrvoje Matijakovic (hrvojem) |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PS-1908