summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* more test added10.5-order_by_limitVarun Gupta2020-04-152-0/+95
|
* Self reviewVarun Gupta2020-04-1511-260/+232
|
* Fixing buildbot failuresVarun Gupta2020-02-186-29/+29
|
* fixing sort_nest.testVarun Gupta2020-02-173-1292/+483
|
* Fixing tests for sort nestVarun Gupta2020-02-175-180/+15
|
* MDEV-21713: LIMIT optimization and selectivity: pessimistic estimates cause ↵Sergei Petrunia2020-02-167-3/+155
| | | | | | | | optimistic plans Don't use LIMIT-based query plans if we don't have an accurate estimate of join output cardinality (the primary reason for that is lack of data about condition selectivity).
* Fixing a minor performance regressionVarun Gupta2020-02-091-1/+1
|
* Minor fixes after rebasing on 10.5Varun Gupta2020-02-091-3/+2
|
* Fixing optimizer trace tests failingVarun Gupta2020-02-091-2/+1
|
* Fix to address performance regression of ORDER BY with limit queriesVarun Gupta2020-02-094-31/+52
|
* Extend the join prefix to ensure all tables in the duplicate range either ↵Varun Gupta2020-02-096-14/+177
| | | | are inside or outside the sort nest
* Adding more test coverageVarun Gupta2020-02-092-0/+34
|
* Improved the descriptionVarun Gupta2020-02-091-56/+57
|
* Adding sql_sort_nest.cc file to CMakeListVarun Gupta2020-02-091-0/+1
|
* Introduced optimizer_switch for cost based order by limit optimizationVarun Gupta2020-02-092-4/+3
|
* Minor fix for duplicate weedoutVarun Gupta2020-02-092-6/+27
|
* Introduced an optimizer_switch for ORDER BY LIMITVarun Gupta2020-02-098-1212/+20
|
* Updated the descriptionVarun Gupta2020-02-091-24/+18
|
* Tests moved to one fileVarun Gupta2020-02-098-1464/+1391
|
* Minor fix to testsVarun Gupta2020-02-094-226/+223
|
* More tests added for subqueriesVarun Gupta2020-02-092-112/+352
|
* Sort nest not allowed inside dependent subqueriesVarun Gupta2020-02-093-7/+184
|
* minor fixVarun Gupta2020-02-094-6/+8
|
* ORDER BY LIMITVarun Gupta2020-02-0940-472/+9061
|
* MDEV-21689 Add Sql_cmd for GRANT/REVOKE statementsAlexander Barkov2020-02-0813-317/+813
| | | | | | | | | | | | | | | | | | | | | Rewriting GRANT/REVOKE grammar to use more bison stack and use Sql_cmd_ style 1. Removing a few members from LEX: - uint grant, grant_to_col, which_columns - List<LEX_COLUMN> columns - bool all_privileges 2. Adding classes Grand_object_name, Lex_grant_object_name 3. Adding classes Grand_privilege, Lex_grand_privilege 4. Adding struct Lex_column_list_privilege_st, class Lex_column_list_privilege 5. Rewriting the GRANT/REVOKE grammar to use new classes and pass them through bison stack (rather than directly access LEX members) 6. Adding classes Sql_cmd_grant* and Sql_cmd_revoke*, changing GRANT/REVOKE to use LEX::m_sql_cmd. 7. Adding the "sp_handler" grammar rule and removing some duplicate grammar for GRANT/REVOKE for different kinds of SP objects. 8. Adding a new rule comma_separated_ident_list, reusing it in: - with_column_list - colum_list_privilege
* Cleanup: Aligned InnoDB index page header accessMarko Mäkelä2020-02-086-149/+78
| | | | | | | | | | | | | | | | | | | ut_align_down(): Preserve the const qualifier. Use C++ casts. ha_delete_hash_node(): Correct an assertion expression. fil_page_get_type(): Perform an assumed-aligned read. page_align(): Preserve the const qualifier. Assume (some) alignment. page_get_max_trx_id(): Check the index page type. page_header_get_field(): Perform an assumed-aligned read. page_get_autoinc(): Perform an assumed-aligned read. page_dir_get_nth_slot(): Perform an assumed-aligned read. Preserve the const qualifier.
* MDEV-21351: Allocate aligned memoryMarko Mäkelä2020-02-082-4/+11
| | | | recv_sys_t::ALIGNMENT: The recv_sys_t::alloc() alignment
* MDEV-21248: Do not break the build on clangMarko Mäkelä2020-02-081-1/+1
|
* MDEV-21248: Prevent optimizing out buf argument in check_stack_overrun.Martin Liska2020-02-081-2/+11
| | | | | | When using LTO, one can see optimization of stack variables that are passed to check_stack_overrun as argument buf. That prevents proper stack overrun detection.
* One more fixup for sizeof(mtr_t) reductionMarko Mäkelä2020-02-071-2/+2
| | | | Add explicit casts when assigning ulint to m_user_space_id.
* mtr_t::get_log_mode(): Remove a redundant assertionMarko Mäkelä2020-02-071-1/+0
| | | | mtr_log_t and mtr_t::m_log_mode have the same range 0 to 3.
* Fixup the parent commitMarko Mäkelä2020-02-071-2/+2
| | | | | | mtr_t::get_log_mode(): Use equivalent static_assert(). mtr_t::m_n_log_recs: Do not exceed the number of bits in uint16_t.
* Cleanup: Recude sizeof(mtr_t)Marko Mäkelä2020-02-072-66/+51
| | | | | | Use bit-fields for some mtr_t members to improve locality of reference. Because mtr_t is never shared between threads, there are no considerations regarding concurrent access.
* Merge 10.4 into 10.5Marko Mäkelä2020-02-0769-294/+587
|\
| * MDEV-21616: Server crash when using "SET STATEMENT max_statement_time=0 FOR ↵Oleksandr Byelkin2020-02-053-0/+26
| | | | | | | | | | | | desc xxx" lead to collapse Main select should be pushed first.
| * MDEV-21658 Error on online ADD PRIMARY KEY after instant DROP/reorderMarko Mäkelä2020-02-053-4/+61
| | | | | | | | | | | | | | | | row_log_table_get_pk_old_col(): For replacing a NULL value for a column of the being-added primary key, look up the correct default value, even if columns had been instantly reordered or dropped earlier. This ought to have been broken ever since commit 0e5a4ac2532c64a545796c787354dc41d61d0e62 (MDEV-15562).
| * MDEV-21645 SIGSEGV in innobase_get_computed_valueMarko Mäkelä2020-02-043-1/+23
| | | | | | | | | | | | ha_innobase::commit_inplace_alter_table(): After ALTER_STORED_COLUMN_ORDER, ensure that the virtual column metadata will be reloaded also when the table is not being rebuilt.
| * MDEV-20625 : MariaDB asserting when enabling wsrep_onbb-10.4-MDEV-20625Jan Lindström2020-02-043-11/+14
| | | | | | | | | | | | | | We need to release global system variables mutex before doing wsrep_init to avoid race with next show status and we need to save wsrep_on value as it is changed on wsrep_init. Added test case.
| * MDEV-20625: MariaDB asserting when enabling wsrep=onJulius Goryavsky2020-02-043-0/+21
| |
| * MDEV-20625 : MariaDB asserting when enabling wsrep_onJan Lindström2020-02-031-48/+68
| | | | | | | | | | When wsrep_on is changed to ON we might need to run wsrep_init if wsrep-provider is set and wsrep is not inited.
| * MDEV-20001 Potential dangerous regression: INSERT INTO >=100 rows fail for ↵Sachin2020-02-039-70/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | myisam table with HASH indexes Problem:- So the issue is when we do bulk insert with rows > MI_MIN_ROWS_TO_DISABLE_INDEXES(100) , We try to disable the indexes to speedup insert. But current logic also disables the long unique indexes. Solution:- In ha_myisam::start_bulk_insert if we find long hash index (HA_KEY_ALG_LONG_HASH) we will not disable the index. This commit also refactors the mi_disable_indexes_for_rebuild function, Since this is function is called at only one place, it is inlined into start_bulk_insert mi_clear_key_active is added into myisamdef.h because now it is also used in ha_myisam.cc file. (Same is done for Aria Storage engine)
| * MDEV-17798 System variable system_versioning_asof accepts wrong values (10.4)Aleksey Midenkov2020-02-023-2/+39
| |
| * MDEV-18791 Wrong error upon creating Aria table with long index on BLOBSachin Setiya2020-02-023-0/+13
| | | | | | | | | | If we have long unique key for aria engine return too long key error, because Aria does not support key on virtual generated column.
| * MDEV-21256 after-merge fix: Use std::atomicMarko Mäkelä2020-02-012-7/+6
| | | | | | | | | | Starting with MariaDB Server 10.4, C++11 is being used. Hence, std::atomic should be preferred to my_atomic.
| * MDEV-19845: Make my_cpu.h self-containedMarko Mäkelä2020-02-013-5/+10
| | | | | | | | Fix up commit f5c080c7353cc9c30d0b269c07024cd38253c3bc
| * MDEV-17844 recs_off_validate() fails in page_zip_write_trx_id_and_roll_ptr()Marko Mäkelä2020-01-311-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 0e5a4ac2532c64a545796c787354dc41d61d0e62 (MDEV-15562) we introduced was a bogus debug check failure that does not affect the correctness of the release build. With a fixed-length PRIMARY KEY, we do not have to recompute the rec_get_offsets() after restarting the mini-transaction, because the offsets of DB_TRX_ID,DB_ROLL_PTR are not going to change. row_undo_mod_clust(): Invoke rec_offs_make_valid() to keep the debug check in page_zip_write_trx_id_and_roll_ptr() happy. The scenario to reproduce this bug should be rather unlikely: In the time frame when row_undo_mod_clust() has committed its first mini-transaction and has not yet started the next one, another mini-transaction must do something that causes the page to be reorganized, split or merged.
| * Fixup cd2c0e013ccb5f9b009743dfd7188585a539d9b5Marko Mäkelä2020-01-311-1/+1
| | | | | | | | | | The variable 'dlh' was being used uninitialized if WSREP_PROVIDER is not set.
| * Empty commitSachin2020-01-310-0/+0
| |
| * Fixed compiler warnings from gcc 7.4.1Monty2020-01-2947-197/+282
| | | | | | | | - Fixed possible error in rocksdb/rdb_datadic.cc
| * Added error output wsrep_print_versionMonty2020-01-291-5/+16
| | | | | | | | This helps to determinate why galera library doesn't load