Details
Description
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
MDEV-6942 SET SESSION statement combined with SET STATEMENT has no effect if it's executed for the same variable
-
- Stalled
-
-
MDEV-6940 SET STATEMENT executed after SET GLOBAL does not work
-
- Closed
-
-
MDEV-6941 SET STATEMENT affects the value of the GLOBAL variable for the duration of the statement
-
- Closed
-
-
MDEV-6945 SET STATEMENT autocommit=... has no effect and causes warnings in the error log
-
- Closed
-
-
MDEV-6946 Assertion `0' failed in mysql_execute_command on SET STATEMENT keycache1.key_buffer_size=.. FOR
-
- Closed
-
-
MDEV-6948 SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id)
-
- Closed
-
-
MDEV-6956 SET STATEMENT default_master_connection = ... has no effect
-
- Closed
-
-
MDEV-6957 SET STATEMENT skip_replication = .. makes the binary log non-replayable
-
- Closed
-
-
MDEV-6976 Assertion `! is_set() || m_can_overwrite_status' failed in Diagnostics_area::set_error_status on SET STATEMENT debug_sync
-
- Closed
-
-
MDEV-6996 SET STATEMENT default_week_format = .. has no effect
-
- Closed
-
-
MDEV-6997 SET STATEMENT last_insert_id FOR ... does not affect the value written to the binlog
-
- Closed
-
-
MDEV-7002 SET STATEMENT sql_log_off has no effect
-
- Closed
-
-
MDEV-7006 SET STATEMENT does not work with slow log tuning (long_query_time, log_slow_filter, log_slow_verbosity, log_slow_rate_limit)
-
- Closed
-
-
MDEV-7007 SET STATEMENT slow_query_log has no effect
-
- Closed
-
-
MDEV-7009 SET STATEMENT min_examined_row_limit has no effect
-
- Closed
-
-
MDEV-7012 SET STATEMENT character_set_client, character_set_connection, character_set_filesystem, collation_connection have no effect
-
- Closed
-
-
MDEV-7015 SET STATEMENT old_passwords has no effect
-
- Closed
-
-
MDEV-6944 SQL_MODEs related to parsing are not applied during execution of the actual statement under SET STATEMENT .. FOR
-
- Closed
-
-
MDEV-6949 MySQL client does not recognize SET STATEMENT .. FOR USE <db name> as a schema change
-
- Closed
-
-
MDEV-6953 SET STATEMENT profiling = .. FOR does not have any effect
-
- Closed
-
-
MDEV-6954 SET STATEMENT rand_seedX = ...FOR ... makes the next rand() to return 0
-
- Closed
-
-
MDEV-6955 SET STATEMENT tx_isolation = FOR ... inside a transaction is meaningless and cannot have any effect, but is allowed
-
- Closed
-
-
MDEV-6977 SET STATEMENT query_cache_type apparently has no effect and hence should be disallowed
-
- Closed
-
-
MDEV-7018 SET STATEMENT query_response_time_exec_time_debug has no effect
-
- Closed
-
-
MDEV-6951 Erroneous SET STATEMENT produces two identical errors
-
- Closed
-
-
MDEV-7013 SET STATEMENT wait_timeout or interactive_timeout seem meaningless
-
- Closed
-
-
MDEV-8185 Variables related to query cache are useless in SET STATEMENT
-
- Open
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Currently in the "standard" configuration (Linux, normal server with XtraDB, no additional plugins) we have 148 variables which are not read-only and have session scope.
As of
10 are already disabled for SET STATEMENT (cause ER_SET_STATEMENT_NOT_SUPPORTED).
From the remaining ones, I tried about a half – not like tested them deeply, but at least checked that they do something more than just display their value in a SELECT under SET STATEMENT ... FOR.
Out of this half, about 2/3 worked and 1/3 didn't.
This gives enough information for further interpolation.
Bugs for discovered failures have been filed.
Most of failures are reproducible with Percona server, but not all of them.
Bugs reproducible on Percona server are also filed in their LP.
Attached is a rough test case for all variables (including read-only, global and unsupported). The windows version is the same as Linux minus several variables that do not exist on Windows.