summaryrefslogtreecommitdiff
path: root/mysql-test/r/mysqld--help.result
Commit message (Collapse)AuthorAgeFilesLines
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-1687/+0
|
* MDEV-11952 Oracle-style packages: stage#5mariadb-10.3.5bb-10.3-compatibilityAlexander Barkov2018-02-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - CREATE PACKAGE [BODY] statements are now entirely written to mysql.proc with type='PACKAGE' and type='PACKAGE BODY'. - CREATE PACKAGE BODY now supports IF NOT EXISTS - DROP PACKAGE BODY now supports IF EXISTS - CREATE OR REPLACE PACKAGE [BODY] is now supported - CREATE PACKAGE [BODY] now support the DEFINER clause: CREATE DEFINER user@host PACKAGE pkg ... END; CREATE DEFINER user@host PACKAGE BODY pkg ... END; - CREATE PACKAGE [BODY] now supports SQL SECURITY and COMMENT clauses, e.g.: CREATE PACKAGE p1 SQL SECURITY INVOKER COMMENT "comment" AS ... END; - Package routines are now created from the package CREATE PACKAGE BODY statement and don't produce individual records in mysql.proc. - CREATE PACKAGE BODY now supports package-wide variables. Package variables can be read and set inside package routines. Package variables are stored in a separate sp_rcontext, which is cached in THD on the first packate routine call. - CREATE PACKAGE BODY now supports the initialization section. - All public routines (i.e. declared in CREATE PACKAGE) must have implementations in CREATE PACKAGE BODY - Only public package routines are available outside of the package - {CREATE|DROP} PACKAGE [BODY] now respects CREATE ROUTINE and ALTER ROUTINE privileges - "GRANT EXECUTE ON PACKAGE BODY pkg" is now supported - SHOW CREATE PACKAGE [BODY] is now supported - SHOW PACKAGE [BODY] STATUS is now supported - CREATE and DROP for PACKAGE [BODY] now works for non-current databases - mysqldump now supports packages - "SHOW {PROCEDURE|FUNCTION) CODE pkg.routine" now works for package routines - "SHOW PACKAGE BODY CODE pkg" now works (the package initialization section) - A new package body level MDL was added - Recursive calls for package procedures are now possible - Routine forward declarations in CREATE PACKATE BODY are now supported. - Package body variables now work as SP OUT parameters - Package body variables now work as SELECT INTO targets - Package body variables now support ROW, %ROWTYPE, %TYPE
* remove @@system_versioning_innodb_algorithm_simpleSergei Golubchik2018-02-241-5/+0
| | | | and delete few garbage-in-garbage-out tests
* MDEV-13417 UPDATE produces wrong values if an updated column is later used ↵Jerome Brauge2018-02-121-1/+1
| | | | | | | | as an update source Standard compatible behavior for UPDATE: all assignments in SET are executed "simultaneously", not left-to-right. And `SET a=b,b=a` will swap the values.
* remove "Transaction-based system versioning is EXPERIMENTAL" warningSergei Golubchik2018-01-131-4/+0
| | | | | | | | | | and the system_versioning_transaction_registry variable. The user enables transaction registry by specifying BIGINT for row_start/row_end columns. check mysql.transaction_registry structure on the first open, not on startup. Avoid warnings unless transaction_registry is actually used.
* System Versioning 1.0 pre8Aleksey Midenkov2018-01-101-7/+2
|\ | | | | | | Merge branch '10.3' into trunk
| * This is a full cost-based implementation of the optimization that employsIgor Babaev2017-12-301-2/+2
| | | | | | | | | | splitting technique for equi-joins of materialized derived tables/views/CTEs. (see mdev-13369 and mdev-13389).
| * @@in_predicate_conversion_thresholdSergei Golubchik2017-12-211-5/+0
| | | | | | | | | | | | * rename in_subquery_conversion_threshold to in_predicate_conversion_threshold * make it debug-only, hide from users * change from ulong to uint - same type and range on all architectures
* | Daemon: debug_system_versioning_show, debug_system_versioning_forceAleksey Midenkov2018-01-101-4/+0
| |
* | SQL: derived, hiding, error messagesSergei Golubchik2018-01-091-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many related changes. Note that AS OF condition must always be pushed down to physical tables, it cannot be applied to a derived or a view. Thus: * no versioning for internal temporary tables, they can never store historical data. * remove special versioning code from mysql_derived_prepare and remove ER_VERS_DERIVED_PROHIBITED - derived can have no historical data and cannot be prohibited for system versioning related reasons. * do not expand select list for derived/views with sys vers fields, derived/views can never have historical data. * remove special invisiblity rules for sys vers fields, they are no longer needed after the previous change * remove system_versioning_hide, it lost the meaning after the previous change. * remove ER_VERS_SYSTEM_TIME_CLASH, it's no "clash", the inner AS OF clause always wins. * non-versioned fields in a historical query reword the warning text, downgrade to note, don't replace values with NULLs
* | Tests: full test results [#387]Aleksey Midenkov2017-12-211-20/+25
| |
* | System Versioning 1.0 pre7Aleksey Midenkov2017-12-211-0/+36
|\ \ | |/ | | | | Merge branch '10.3' into trunk
| * MDEV-13073. This is a part with a new test (refined Ali'sAndrei Elkin2017-12-181-0/+8
| | | | | | | | | | | | | | | | | | one) and affected result files. Specifically to rpl_semi_sync_after_sync*, the changed results reflect a fact that thanks to fixes in the dump thread functionality there's no longer zombie thread to kill neither such thread represent a semisync client (so the counter drops).
| * Moved semisync from a plugin to normal serverMonty2017-12-181-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | Part of MDEV-13073 AliSQL Optimize performance of semisync Did the following renames to match other similar variables key_ss_mutex_LOCK_binlog_ > key_LOCK_bing key_ss_cond_COND_binlog_send_ -> key_COND_binlog_send COND_binlog_send_ -> COND_binlog_send LOCK_binlog_ -> LOCK_binlog debian/mariadb-server-10.2.install does not install semisync libs.
* | System Versioning 1.0 pre3Aleksey Midenkov2017-12-111-5/+17
|\ \ | |/ | | | | Merge branch '10.3' into trunk
| * MDEV-12501 -- set --maturity-level by defaultVesa Pentti2017-12-091-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Note: breaking change; since this commit, a plugin that has worked so far might get rejected due to plugin maturity * mariabackup is not affected (allows all plugins) * VERSION file defines SERVER_MATURITY, which defines the corresponding numeric value as SERVER_MATURITY_LEVEL in include/mysql_version.h * The default value for 'plugin_maturity' is SERVER_MATURITY_LEVEL - 1 * Logs a warning if a plugin has maturity lower than SERVER_MATURITY_LEVEL * Tests suppress the plugin maturity warning * Tests use --plugin-maturity=unknown by default so as not to fail due to the stricter plugin maturity handling
| * Revert "MDEV-12501 -- set --maturity-level by default"Vesa Pentti2017-12-051-0/+1
| | | | | | | | This reverts commit 1af2d7ba235305ffd4c24a47cccafd5fe6815d9e.
| * MDEV-12501 -- set --maturity-level by defaultVesa Pentti2017-12-041-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Note: breaking change; since this commit, a plugin that has worked so far might get rejected due to plugin maturity * mariabackup is not affected (allows all plugins) * VERSION file defines SERVER_MATURITY, which defines the corresponding numeric value as SERVER_MATURITY_LEVEL in include/mysql_version.h * The default value for 'plugin_maturity' is SERVER_MATURITY_LEVEL - 1 * Logs a warning if a plugin has maturity lower than SERVER_MATURITY_LEVEL * Tests suppress the plugin maturity warning * Tests use --plugin-maturity=unknown by default so as not to fail due to the stricter plugin maturity handling
| * MDEV-7702 Spiral patch 004_mariadb-10.0.15.slave-trx-retry.diffMonty2017-12-031-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is about adding more options to force slave retries Two new variables has been added: slave_transaction_retry_errors - Tells the slave thread to retry transaction for replication when a query event returns an error from the provided list. Deadlock and elapsed lock wait timeout errors are automatically added to this list slave-transaction-retry-interval - Interval of the slave SQL thread will retry a transaction in case it failed with a deadlock or elapsed lock wait timeout or listed in slave_transaction_retry_errors Other changes: - Simplifed code for slave_skip_errors (to be aligned with slave_transaction_retry_errors) - Renamed print_slave_skip_errors() to make_slave_skip_errors_printable() - Remove printing error from init_slave_skip_errors as my_bitmap_init() will do that if needed. - Generalize has_temporary_error()
| * Removed "deprecated" warning from explicit_defaults_for_timestampMichael Widenius2017-11-241-1/+1
| |
* | SQL: versioning_alter_history ERROR mode [closes #350]Aleksey Midenkov2017-11-271-4/+3
| | | | | | | | Disabled DROP and SURVIVE modes.
* | System Versioning 1.0pre2Aleksey Midenkov2017-11-231-0/+21
|\ \ | |/ | | | | Merge branch '10.3' into trunk
| * MDEV-14412 Support TCP keepalive optionsVladislav Vaintroub2017-11-171-0/+18
| | | | | | | | | | Based on pull request by Oleg Obleukhov https://github.com/MariaDB/server/pull/400
| * MDEV-14114 Intoduce variable for binlog io cache size.Vladislav Vaintroub2017-11-171-0/+3
| |
* | SQL,Client: mysqldump for TRT fix [#302]Aleksey Midenkov2017-11-171-0/+4
| | | | | | | | | | | | | | | | | | Test results: main. mysqldump mysqldump-max mysqld--help openssl_1
* | Tests: full test resultsEugene Kosov2017-11-131-2/+0
| | | | | | | | | | | | | | | | innodb.innodb-index-online-fk innodb.instant_alter_debug innodb.innodb_skip_innodb_is_tables sys_vars.sysvars_server_notembedded main.mysqld--help
* | SQL, Test: main suite [fixes #300]Aleksey Midenkov2017-11-131-0/+19
|/
* Merge bb-10.2-ext into 10.3Marko Mäkelä2017-11-101-1/+1
|\
| * Add more execution stages (commit, rollback, etc)Monty2017-11-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was done to get more information about where time is spent. Now we can get proper timing for time spent in commit, rollback, binlog write etc. Following stages was added: - Commit - Commit_implicit - Rollback - Rollback implicit - Binlog write - Init for update - This is used instead of "Init" for insert, update and delete. - Staring cleanup Following stages where changed: - "Unlocking tables" stage reset stage to previous stage at end - "binlog write" stage resets stage to previous stage at end - "end" -> "end of update loop" - "cleaning up" -> "Reset for next command" - Added stage_searching_rows_for_update when searching for rows to be deleted. Other things: - Renamed all stages to start with big letter (before there was no consitency) - Increased performance_schema_max_stage_classes from 150 to 160. - Most of the test changes in performance schema comes from renaming of stages. - Removed duplicate output of variables and inital state in a lot of performance schema tests. This was done to make it easier to change a default value for a performance variable without affecting all tests. - Added start_server_variables.test to check configuration - Removed some duplicate "closing tables" stages - Updated position for "stage_init_update" and "stage_updating" for delete, insert and update to be just before update loop (for more exact timing). - Don't set "Checking permissions" twice in a row. - Remove stage_end stage from creating views (not done for create table either). - Updated default performance history size from 10 to 20 because of new stages - Ensure that ps_enabled is correct (to be used in a later patch)
* | Adjusted tests after changing the default value forIgor Babaev2017-11-031-1/+1
| | | | | | | | the system variable @@in_subquery_conversion_threshold
* | Merge bb-10.2-ext into 10.3Marko Mäkelä2017-11-021-2/+3
|\ \ | |/
| * Merge 10.2 into bb-10.2-extMarko Mäkelä2017-11-011-2/+3
| |\
| | * Updated help message for long_query_timeMonty2017-10-311-2/+3
| | |
* | | Merge remote-tracking branch 'shagalla/10.3-mdev12172' into 10.3Igor Babaev2017-11-011-0/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | As a result of this merge the code for the following tasks appears in 10.3: - MDEV-12172 Implement tables specified by table value constructors - MDEV-12176 Transform [NOT] IN predicate with long list of values INTO [NOT] IN subquery.
| * | | Mistakes corrected. Test results corrected.Galina Shalygina2017-10-291-1/+1
| | | |
| * | | Mistakes corrected.Galina Shalygina2017-10-281-0/+5
| | | | | | | | | | | | | | | | | | | | TVC can be used in IN subquery and in PARTITION BY struct now. Special variable to control working of optimization added.
* | | | Merge remote-tracking branch 'origin/bb-10.2-ext' into 10.3Alexander Barkov2017-10-301-1/+2
|\ \ \ \ | | |/ / | |/| | | | | | TODO: enable MDEV-13049 optimization for 10.3
| * | | MDEV-14013 : sql_mode=EMPTY_STRING_IS_NULLhalfspawn2017-10-141-1/+2
| | | |
* | | | MDEV-13675 filsort_priority_queueSergei Golubchik2017-10-051-2/+2
| | | | | | | | | | | | | | | | typo fixed
* | | | Merge remote-tracking branch 'origin/bb-10.2-ext' into 10.3Alexander Barkov2017-09-281-3/+4
|\ \ \ \ | |/ / /
| * | | Merge remote-tracking branch 'origin/10.2' into bb-10.2-extAlexander Barkov2017-09-281-3/+4
| |\ \ \ | | | |/ | | |/|
| | * | Moved autosetting of host_cache_size and back_log to proper placebb-10-3-markoMonty2017-09-261-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | - Clean up formulas and comments for host_cache_size and back_log - Added test of autoset (for host_cache_size) - Marked open_files_limit as auto_set
* | | | MDEV-13855 - Rename idle_readwrite_transaction_timeout toSergey Vojtovich2017-09-221-4/+4
| | | | | | | | | | | | | | | | idle_write_transaction_timeout
* | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2017-09-011-1/+1
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into bb-10.2-extMarko Mäkelä2017-09-011-1/+1
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2Marko Mäkelä2017-08-311-1/+1
| | |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For running the Galera tests, the variable my_disable_leak_check was set to true in order to avoid assertions due to memory leaks at shutdown. Some adjustments due to MDEV-13625 (merge InnoDB tests from MySQL 5.6) were performed. The most notable behaviour changes from 10.0 and 10.1 are the following: * innodb.innodb-table-online: adjustments for the DROP COLUMN behaviour change (MDEV-11114, MDEV-13613) * innodb.innodb-index-online-fk: the removal of a (1,NULL) record from the result; originally removed in MySQL 5.7 in the Oracle Bug #16244691 fix https://github.com/mysql/mysql-server/commit/377774689bf6a16af74182753fe950d514c2c6dd * innodb.create-index-debug: disabled due to MDEV-13680 (the MySQL Bug #77497 fix was not merged from 5.6 to 5.7.10) * innodb.innodb-alter-autoinc: MariaDB 10.2 behaves like MySQL 5.6/5.7, while MariaDB 10.0 and 10.1 assign different values when auto_increment_increment or auto_increment_offset are used. Also MySQL 5.6/5.7 exhibit different behaviour between LGORITHM=INPLACE and ALGORITHM=COPY, so something needs to be tested and fixed in both MariaDB 10.0 and 10.2. * innodb.innodb-wl5980-alter: disabled because it would trigger an InnoDB assertion failure (MDEV-13668 may need additional effort in 10.2)
| | | * \ Merge branch '10.0' into 10.1Marko Mäkelä2017-08-301-1/+1
| | | |\ \
| | | | * | MDEV-13583 Improvements for MTR rebootstrap introduced in MDEV-12042Elena Stepanova2017-08-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - make re-bootstrap run with all extra options, not only InnoDB ones - re-use previously created bootstrap.sql - add --console - fix debian patch to keep it applicable
* | | | | | MDEV-11371 - column compressionSergey Vojtovich2017-08-311-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Storage engine independent support for column compression. TINYBLOB, BLOB, MEDIUMBLOB, LONGBLOB, TINYTEXT, TEXT, MEDIUMTEXT, LONGTEXT, VARCHAR and VARBINARY columns can be compressed. New COMPRESSED column attribute added: COMPRESSED[=<compression_method>] System variables added: column_compression_threshold column_compression_zlib_level column_compression_zlib_strategy column_compression_zlib_wrap Status variables added: Column_compressions Column_decompressions Limitations: - the only supported method currently is zlib - CSV storage engine stores data uncompressed on-disk even if COMPRESSED attribute is present - it is not possible to create indexes over compressed columns.
* | | | | | Merge branch 'bb-10.2-ext' into 10.3Sergei Golubchik2017-08-261-19/+32
|\ \ \ \ \ \ | |/ / / / /
View Lorry Controller Status