microslow patch long_query_time backwards compatibility?
Bug #288062 reported by
Arjen Lentz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OurDelta |
Fix Released
|
High
|
Arjen Lentz |
Bug Description
Check percona/microslow patch to be backwards compatible, so an existing user upgrading to OurDelta won't see changed behaviour by default.
The my.cnf options are processed and assigned automatically so we probably can't get in there.
But before it's used, we can see if it's say < 600 (10 minutes in old form!) and do *1000000 to convert it to microseconds.
Should be perfectly safe.
Related branches
lp:~ourdelta-core/ourdelta/ourdelta-percona-d6-mysql50
- OurDelta-core: Pending requested
Changed in ourdelta: | |
assignee: | nobody → arjen-lentz |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in ourdelta: | |
status: | In Progress → Fix Committed |
Changed in ourdelta: | |
assignee: | erik-ibiblio → arjen-lentz |
status: | In Progress → Fix Committed |
To post a comment you must log in.
In mysqld.cc, get_one_option() function, adding in:
+ case OPT_LONG_ QUERY_TIME: system_ variables. long_query_ time < 600) system_ variables. long_query_ time *= 1000000;
+ /*
+ Fix up low values to ensure backward compatibility in microslow patch:
+ if long_query_time < 600 (10 minutes in old granularity)
+ then we simply adjust it for microseconds.
+ */
+ if (global_
+ global_
+ break;
that should do the trick cleanly. percona- d6-mysql50 branch for testing.
Modified in ourdelta-