summaryrefslogtreecommitdiff
path: root/sql/sys_vars.cc
Commit message (Collapse)AuthorAgeFilesLines
* Updated code to be compiled with columnstore and boostMonty2021-02-171-1/+1
| | | | | | | | - Updated to use temporary CS branch develop:monty-10.6 - Renamed set_bits in my_global to my_setbits as set_bits conclicts with boost - Renamed my_bit.h:my_set_bits to my_set_low_bits to avoid confusion with my_setbits and also to more clearly reflect what the function does.
* Change CHARSET_INFO character set and collaction names to LEX_CSTRINGMonty2021-01-281-10/+10
| | | | | | | | | | | | | | | | | | | | | | This change removed 68 strlen() calls from the code. The following renames was to ensure we don't use the old names when merging code from earlier releases, as using the new variables for print function could result in crashes: - charset->csname renamed to charset->cs_name - charset->name renamed to charset->col_name Almost everything where mechanical changes except: - Changed to use the new Protocol::store(LEX_CSTRING..) when possible - Changed to use field->store(LEX_CSTRING*, CHARSET_INFO*) when possible - Changed to use String->append(LEX_CSTRING&) when possible Other things: - There where compiler issues with ensuring that all character set names points to the same string: gcc doesn't allow one to use integer constants when defining global structures (constant char * pointers works fine). To get around this, I declared defines for each character set name length.
* MDEV-24546 : AddressSanitizer: initialization-order-fiasco on address ... in ↵Jan Lindström2021-01-091-2/+4
| | | | | | | | Sys_var_integer from __static_initialization_and_destruction_0, possibly inside global var wsrep_gtid_server Galera parameter wsrep_gtid_domain_id was defined using a class where actual parameter was not a first member. Fixed this by using normal variable and assigning this value to class member value.
* Merge commit '10.4' into 10.5Oleksandr Byelkin2021-01-061-3/+3
|\
| * Merge branch '10.3' into 10.4bb-10.4-MDEV-23468Oleksandr Byelkin2020-12-251-3/+3
| |\
| | * Merge branch '10.2' into 10.3Oleksandr Byelkin2020-12-231-3/+3
| | |\
| | | * MDEV-4677 GROUP_CONCAT not showing any output with group_concat_max_len >= 4GbSergei Golubchik2020-12-101-2/+2
| | | | | | | | | | | | | | | | | | | | don't allow group_concat_max_len values >= 4Gb (they never worked anyway)
| | | * MDEV-24033: SIGSEGV in __memcmp_avx2_movbe from queue_insert | SIGSEGV in ↵Sergei Golubchik2020-12-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | __memcmp_avx2_movbe from native_compare don't allow too small max_sort_length values
* | | | Merge 10.4 into 10.5Marko Mäkelä2020-12-021-1/+1
|\ \ \ \ | |/ / /
| * | | Merge 10.3 into 10.4Marko Mäkelä2020-12-011-1/+1
| |\ \ \ | | |/ /
| | * | Merge 10.2 into 10.3Marko Mäkelä2020-12-011-1/+1
| | |\ \ | | | |/
| | | * MDEV 15532 Assertion `!log->same_pk' failed in row_log_table_apply_deleteMonty2020-11-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The reason for the failure is that thd->mdl_context.release_transactional_locks() was called after commit & rollback even in cases where the current transaction is still active. For 10.2, 10.3 and 10.4 the fix is simple: - Replace all calls to thd->mdl_context.release_transactional_locks() with thd->release_transactional_locks(). The thd function will only call the mdl_context function if there are no active transactional locks. In 10.6 we will better fix where we will change the return value for some trans_xxx() functions to indicate if transaction did close the transaction or not. This will avoid the need of the indirect call. Other things: - trans_xa_commit() and trans_xa_rollback() will automatically call release_transactional_locks() if the transaction is closed. - We can't do that for the other functions as the caller of many of these are doing additional work (like close_thread_tables) before calling release_transactional_locks(). - Added missing abort_result_set() and missing DBUG_RETURN in select_create::send_eof() - Fixed wrong indentation in injector::transaction::commit()
| * | | Merge 10.3 into 10.4Marko Mäkelä2020-10-291-1/+1
| |\ \ \ | | |/ /
| | * | Merge 10.2 into 10.3Marko Mäkelä2020-10-281-1/+1
| | |\ \ | | | |/
| | | * MDEV-23492 performance_schema_digests_size changing from default to 5000 ↵Sergei Golubchik2020-10-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | when enabling performance_schema max allowed value limit should be larger than any auto-sized value
| | | * MDEV-20401: revert unnecessary changeJulius Goryavsky2020-07-161-1/+1
| | | |
| | | * MDEV-20401: Server incorrectly auto-sets lower_case_file_system valueJulius Goryavsky2020-07-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Server auto-sets lower_case_file_system value based on default datadir's behavior instead of instead of using the directory specified by the user through the configuration file or command line options. This patch fixes this problem.
* | | | MDEV-23492 performance_schema_digests_size changing from default to 5000 ↵Sergei Golubchik2020-09-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | when enabling performance_schema max allowed value limit should be larger than any auto-sized value
* | | | Merge 10.4 into 10.5Marko Mäkelä2020-08-011-0/+6
|\ \ \ \ | |/ / /
| * | | Merge 10.3 into 10.4Marko Mäkelä2020-07-311-0/+6
| |\ \ \ | | |/ /
| | * | MDEV-21101 unexpected wait_timeout with pool-of-threadsVladislav Vaintroub2020-07-301-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to restricted size of the threadpool, execution of client queries can be delayed (queued) for a while. This delay was interpreted as client inactivity, and connection is closed, if client idle time + queue time exceeds wait_timeout. But users did not expect queue time to be included into wait_timeout. This patch changes the behavior. We don't close connection anymore, if there is some unread data present on connection, even if wait_timeout is exceeded. Unread data means that client was not idle, it sent a query, which we did not have time to process yet.
* | | | Merge 10.4 into 10.5Marko Mäkelä2020-07-151-2/+13
|\ \ \ \ | |/ / /
| * | | Merge 10.3 into 10.4Marko Mäkelä2020-07-151-2/+13
| |\ \ \ | | |/ /
| | * | Merge 10.2 into 10.3Marko Mäkelä2020-07-141-1/+12
| | |\ \ | | | |/
| | | * MDEV-22058: Assertion `!is_set() || (m_status == DA_OK_BULK && ↵Rucha Deodhar2020-07-121-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | is_bulk_op())' failed in Diagnostics_area::set_ok_status Error state is not stored in check_and_do_in_subquery_rewrites() when there is illegal combination of optimizer switches. So all the functions eventually return false. Thus the assetion failure.
* | | | MDEV-16470: switch off user variables (and fixes of its support)bb-10.5-MDEV-22550Oleksandr Byelkin2020-06-121-0/+2
| | | |
* | | | Merge 10.4 into 10.5Marko Mäkelä2020-06-071-1/+1
|\ \ \ \ | |/ / /
| * | | Merge 10.3 into 10.4Marko Mäkelä2020-06-061-1/+1
| |\ \ \ | | |/ /
| | * | Merge 10.2 into 10.3Marko Mäkelä2020-06-061-1/+1
| | |\ \ | | | |/
| | | * Merge 10.1 into 10.2Marko Mäkelä2020-06-061-1/+1
| | | |\
| | | | * MDEV-22715: SIGSEGV in radixsort_for_str_ptr and in native_compare/my_qsort2 ↵Varun Gupta2020-06-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (optimized builds) For DECIMAL[(M[,D])] datatype max_sort_length was not being honoured which was leading to buffer overflow while making the sort key. The fix to this problem would be to create sort keys for decimals with atmost max_sort_key bytes Important: The minimum value of max_sort_length has been raised to 8 (previously was 4), so fixed size datatypes like DOUBLE and BIGINIT are not truncated for lower values of max_sort_length.
* | | | | Change THD->transaction to a pointer to enable multiple transactionsMonty2020-05-231-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All changes (except one) is of type thd->transaction. -> thd->transaction-> thd->transaction points by default to 'thd->default_transaction' This allows us to 'easily' have multiple active transactions for a THD object, like when reading data from the mysql.proc table
* | | | | Merge 10.4 into 10.5Marko Mäkelä2020-04-251-1/+1
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | The functional changes of commit 5836191c8f0658d5d75484766fdcc3d838b0a5c1 (MDEV-21168) are omitted due to MDEV-742 having addressed the issue.
| * | | | Merge 10.3 into 10.4Marko Mäkelä2020-04-161-1/+1
| |\ \ \ \ | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | In main.index_merge_myisam we remove the test that was added in commit a2d24def8cc42d27c72d833abfb39ef24a2b96ba because it duplicates the test case that was added in commit 5af12e463549e4bbc2ce6ab720d78937d5e5db4e.
| | * | | MDEV-22137 correct documentation of tcp_keepalive_time system variableVladislav Vaintroub2020-04-031-1/+1
| | | | |
* | | | | Merge pull request #1221 from ↵Daniel Black2020-04-021-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | grooverdan/10.4-MDEV-18851-multiple-sized-large-page-support MDEV-18851: multiple sized large page support (linux)
* | | | | Added support for replication for S3Monty2020-03-241-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MDEV-19964 S3 replication support Added new configure options: s3_slave_ignore_updates "If the slave has shares same S3 storage as the master" s3_replicate_alter_as_create_select "When converting S3 table to local table, log all rows in binary log" This allows on to configure slaves to have the S3 storage shared or independent from the master. Other thing: Added new session variable '@@sql_if_exists' to force IF_EXIST to DDL's.
* | | | | MDEV-22012 Allow SET TIMESTAMP for users with GRANT BINLOG REPLAY when ↵Alexander Barkov2020-03-231-4/+1
| | | | | | | | | | | | | | | | | | | | --secure-timestamp=replication
* | | | | MDEV-21975 Add BINLOG REPLAY privilege and bind new privileges to ↵Alexander Barkov2020-03-181-16/+30
| | | | | | | | | | | | | | | | | | | | gtid_seq_no, preudo_thread_id, server_id, gtid_domain_id
* | | | | MDEV-21973 Bind REPLICATION {MASTER|SLAVE} ADMIN to gtid_* GLOBAL-only ↵Alexander Barkov2020-03-181-4/+12
| | | | | | | | | | | | | | | | | | | | system variables
* | | | | MDEV-21972 Bind REPLICATION MASTER ADMIN to master_verify_checksumAlexander Barkov2020-03-181-1/+3
| | | | |
* | | | | MDEV-21971 Bind BINLOG ADMIN to binlog_annotate_row_events and ↵Alexander Barkov2020-03-181-2/+8
| | | | | | | | | | | | | | | | | | | | binlog_row_image global and session variables
* | | | | MDEV-21969 Bind REPLICATION SLAVE ADMIN to relay_log_*, sync_master_info, ↵Alexander Barkov2020-03-181-5/+15
| | | | | | | | | | | | | | | | | | | | sync_relay_log, sync_relay_log_info
* | | | | MDEV-21967 Bind REPLICATION {MASTER|SLAVE} ADMIN to rpl_semi_sync_* variablesAlexander Barkov2020-03-181-9/+27
| | | | |
* | | | | MDEV-21966 Bind REPLICATION SLAVE ADMIN to a number of global system variablesAlexander Barkov2020-03-181-23/+63
| | | | |
* | | | | MDEV-21963 Bind BINLOG ADMIN to a number of global system variablesAlexander Barkov2020-03-171-14/+42
| | | | |
* | | | | MDEV-21961 Bind CONNECTION ADMIN to a number of global system variablesAlexander Barkov2020-03-171-21/+64
| | | | |
* | | | | MDEV-21960 Bind READ_ONLY ADMIN to @@read_onlyAlexander Barkov2020-03-171-1/+3
| | | | |
* | | | | MDEV-21957 Bind BINLOG ADMIN to @@binlog_format, @@binlog_direct_.., ↵Alexander Barkov2020-03-171-12/+12
| | | | | | | | | | | | | | | | | | | | @@sql_log_bin
* | | | | MDEV-21956 Add class Sys_var_charptr_fscsAlexander Barkov2020-03-171-109/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Simplifying definitions on Sys_var_charptr*: - Removing sys_var::is_os_charset - Adding a new class Sys_var_charptr_fscs, to handle system variables with character_set_filesystem.
View Lorry Controller Status