[MDEV-7006] SET STATEMENT does not work with slow log tuning (long_query_time, log_slow_filter, log_slow_verbosity, log_slow_rate_limit) Created: 2014-11-01 Updated: 2015-04-12 Resolved: 2015-03-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Admin statements |
| Affects Version/s: | N/A |
| Fix Version/s: | 10.1.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
The first test case is for 4 options each set via SET STATEMENT var FOR query. Every part of the test fails – whatever is expected does not happen.
All the same in Percona server. |
| Comments |
| Comment by Oleksandr Byelkin [ 2014-11-05 ] |
|
The variables prohibited as a workaround. |
| Comment by Oleksandr Byelkin [ 2014-11-11 ] |
|
Here (as well as all bugs connected to slow log) cause is that we write slow log after restoring variables values. |
| Comment by Oleksandr Byelkin [ 2015-02-17 ] |
|
Hopefully I fixed everything except finding a function to put variables reset (there is no such function and I can't move the calls because they are at the end of statements execution loop. commit to check is: |
| Comment by Oleksandr Byelkin [ 2015-03-10 ] |
|
The review mail is answered, fix according to the review commited |
| Comment by Oleksandr Byelkin [ 2015-03-10 ] |
|
evision-id: 966158a1d718e49fc8c0bbbed8b3078f247f8a33
old values of SET STATENENT variables now saved in its own Query_arena and restored later |
| Comment by Sergei Golubchik [ 2015-03-11 ] |
|
ok to push |
| Comment by Daniel Black [ 2015-04-12 ] |
|
ref: https://github.com/MariaDB/server/commit/a71e2d23bd08ca041a953df44f2235a8ef20bfcc |