{"push_id":4128227509,"size":109,"distinct_size":1,"ref":"refs/heads/bb-10.4-robert","head":"0101b1f8e98a552703639899926216ad17e253cd","before":"e991b112e7dd9c13715dfbe607dcad0951905dd8","commits":[{"sha":"c8dc866fdeee551993ef91fb321135f9106ea00e","author":{"name":"Sergei Petrunia","email":"2684b34324e4c416e773d490feeb83d074e85151@askmonty.org"},"message":"MDEV-20371: Invalid reads at plan refinement stage: join->positions...\n\nbest_access_path() is called from two optimization phases:\n\n1. Plan choice phase, in choose_plan(). Here, the join prefix being\n   considered is in join->positions[]\n\n2. Plan refinement stage, in fix_semijoin_strategies_for_picked_join_order\n   Here, the join prefix is in join->best_positions[]\n\nIt used to access join->positions[] from stage #2. This didnt cause any\nvalgrind or asan failures (as join->positions[] has been written-to before)\nbut the effect was similar to that of reading the random data:\nThe join prefix we've picked (in join->best_positions) could have\nnothing in common with the join prefix that was last to be considered\n(in join->positions).","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/c8dc866fdeee551993ef91fb321135f9106ea00e"},{"sha":"be6beb73e9e6adf2ebd69354a2496817f03ae6ff","author":{"name":"Sergei Petrunia","email":"2684b34324e4c416e773d490feeb83d074e85151@askmonty.org"},"message":"MDEV-16560: [counter] rocksdb.ttl_secondary_read_filtering fail in buildbot\n\nIt is not reproducible, but the issue seems to be the same as with\nMDEV-20490 and rocksdb.ttl_primary_read_filtering - a compaction caused\nby DROP TABLE gets behind and compacts away the expired rows for the next\ntest. Fix this in the same way.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/be6beb73e9e6adf2ebd69354a2496817f03ae6ff"},{"sha":"99ecb33389dd675c5c79928c2ac705585b0c467d","author":{"name":"Vladislav Vaintroub","email":"6ffa87d6c28c4a5be0717cb2fad52329a49c052e@mariadb.com"},"message":"MDEV-20570 : Packaging fails \"The specified timestamp server either could not be reached\"\n\nOn  Windows, during packaging step, if signing fails, retry\nsigntool again without timestamp parameter.\n\nFixes sporadic (rare) failures on buildbot","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/99ecb33389dd675c5c79928c2ac705585b0c467d"},{"sha":"41290e91b7be29ed72b8a41c7b6698ec1d2b96ab","author":{"name":"Vladislav Vaintroub","email":"6ffa87d6c28c4a5be0717cb2fad52329a49c052e@mariadb.com"},"message":"Fix CMake warning in spider, in Windows ninja build","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/41290e91b7be29ed72b8a41c7b6698ec1d2b96ab"},{"sha":"deb9121fdf2152752346c767321e6e01aa5d6c69","author":{"name":"Igor Babaev","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@askmonty.org"},"message":"MDEV-20576 A new assertion added to check validity of calculated\n           selectivity values fails\n\nAfter having set the assertion that checks validity of selectivity values\nreturned by the function table_cond_selectivity() a test case from\norder_by.tesst failed. The failure occurred because range optimizer could\nreturn as an estimate of the cardinality of the ranges built for an index\na number exceeding the total number of records in the table.\n\nThe second bug is more subtle. It may happen when there are several\nindexes with same prefix defined on the first joined table t accessed by\na constant ref access. In this case the range optimizer estimates the\nnumber of accessed records of t for each usable index and these\nestimates can be different. Only the first of these estimates is taken\ninto account when the selectivity of the ref access is calculated.\nHowever the optimizer later can choose a different index that provides\na different estimate. The function table_condition_selectivity() could use\nthis estimate to discount the selectivity of the ref access. This could\nlead to an selectivity value returned by this function that was greater\nthat 1.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/deb9121fdf2152752346c767321e6e01aa5d6c69"},{"sha":"40beeb1402e1bf443eadb2986fd87cd3f0e9ff24","author":{"name":"Teemu Ollakka","email":"119d61b9427ee26cb15bfa01c2be4893be272f5d@galeracluster.com"},"message":"MDEV-20561 Galera node shutdown fails in non-Primary (#1386)\n\nCommand COM_SHUTDOWN was rejected in non-Primary because\r\nserver_command_flags[COM_SHUTDOWN] had value CF_NO_COM_MULTI\r\ninstead of CF_SKIP_WSREP_CHECK.\r\n\r\nAs a fix removed assignment\r\nserver_command_flags[CF_NO_COM_MULTI]= CF_NO_COM_MULTI\r\nwhich overwrote server_command_flags[COM_SHUTDOWN].","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/40beeb1402e1bf443eadb2986fd87cd3f0e9ff24"},{"sha":"3422c13ab748a9da688c00b1b1e522cbcd38d4a7","author":{"name":"Jan Lindström","email":"abe77250017703a420e405c014bb9c0d57a60c8f@mariadb.com"},"message":"Try to fix galera.MW-336 test case.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/3422c13ab748a9da688c00b1b1e522cbcd38d4a7"},{"sha":"3793da44cff600843384d8c5718940d95711511a","author":{"name":"Anel Husakovic","email":"ec29c398e5bbc393bb26da5e91027355d0e7550c@mariadb.org"},"message":"Enable the auto parameter of the flag `default-character-set`\n\nCloses #739\n\nWhen invoking option `--default-character-set=auto` character set\nfrom underlying OS settings should be detected for mysqldump.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/3793da44cff600843384d8c5718940d95711511a"},{"sha":"b214264aee2a6441abc7c8e73519c8267edcb8fa","author":{"name":"Marko Mäkelä","email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@mariadb.com"},"message":"MDEV-20525 rocksdb debug compilation fails on Windows due to unresolved my_assert variable\n\nMYSQL_PLUGIN_IMPORT did not work correctly for the RocksDB helper library\nrocksdb_aux_lib, because that library was not compiled with\n-DMYSQL_DYNAMIC_PLUGIN.\n\nFix DBUG such that it does not depend on exported data, only on functions\n(which do not need MYSQL_PLUGIN_IMPORT decoration)\n\nUse a \"getter\" function _db_my_assert() instead of DLL-exported variable.\n\nAlso, reduce object code duplication by moving more of the DBUG_ASSERT\nlogic inside the _db_my_assert() function, and add unlikely() and\nATTRIBUTE_COLD hints to ensure that the 'assertion failed' code will\nbe separated from the main control flow logic. Thus, the compiler can\nmove the unlikely() code to the end of the compiled function, reachable\nvia a forward conditional branch, which the processor's branch predictor\ncould assume 'not taken'.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/b214264aee2a6441abc7c8e73519c8267edcb8fa"},{"sha":"23657a21018d0b3d0464bbd55236113ebcd3d4b7","author":{"name":"Marko Mäkelä","email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@mariadb.com"},"message":"MDEV-13893/MDEV-12699: Enable encryption.innodb-redo-badkey\n\nThe test had been disabled in 10.2 due to frequent failures,\nin 5ec9b88e11118c798ff2381771a72f76b2b72f9e.\nAfter the problems were addressed, we failed to re-enable the test\nuntil now.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/23657a21018d0b3d0464bbd55236113ebcd3d4b7"},{"sha":"bfbf0f225179d79c1c568b93ddc8b5dd6a670072","author":{"name":"Marko Mäkelä","email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@mariadb.com"},"message":"MDEV-20525: Fix the -std=c90 builds","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/bfbf0f225179d79c1c568b93ddc8b5dd6a670072"},{"sha":"0954bcb6639af47a8b57eb426aee9bba4036e5f1","author":{"name":"Igor Babaev","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@askmonty.org"},"message":"Post fix after the patch for MDEV-20576.\n\nAdjusted test results.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/0954bcb6639af47a8b57eb426aee9bba4036e5f1"},{"sha":"ae2b88ff3f94253921fed5c48422adeebe7e623d","author":{"name":"Igor Babaev","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@askmonty.org"},"message":"Adjusted test results after the change of a test case","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/ae2b88ff3f94253921fed5c48422adeebe7e623d"},{"sha":"2a98d0b5ca2324405d65415423258cc088fa2f8a","author":{"name":"Jan Lindström","email":"abe77250017703a420e405c014bb9c0d57a60c8f@mariadb.com"},"message":"Fix #2 for galera.MW-336","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/2a98d0b5ca2324405d65415423258cc088fa2f8a"},{"sha":"90a9c4cae74d2ef1008e3f216026b7fd2697e46b","author":{"name":"Sujatha","email":"1e8e3bac36d85782b34408b94459da13dba11a6a@mariadb.com"},"message":"MDEV-20217: Semi_sync: Last_IO_Error: Fatal error: Failed to run 'after_queue_event' hook\n\nFix:\n===\nImplemented upstream fix.\n\ncommit 7d3d0fc303183ef50a343680ce70df71d5675cd1\nAuthor: He Zhenxing <zhenxing.he@sun.com>\n\nBackport Bug#45852 Semisynch: Last_IO_Error: Fatal error: Failed\nto run 'after_queue_event' hook\n\nErrors when send reply to master should never cause the IO thread\nto stop, because master can fall back to async replication if it\ndoes not get reply from slave.\n\nThe problem is fixed by deliberately ignoring the return value of\nslave_reply.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/90a9c4cae74d2ef1008e3f216026b7fd2697e46b"},{"sha":"fb3e3a6a3d165d79331f7f359e9c1f28a332c772","author":{"name":"Thirunarayanan Balathandayuthapani","email":"eeee3294f1327533d6d73c46ed1259dedcb2c099@mariadb.com"},"message":"MDEV-20483 trx_lock_t::table_locks is not a subset of trx_lock_t::trx_locks\n\nProblem:\n=======\n  Transaction left with nonempty table locks list. This leads to\nassumption that table_locks is not subset of trx_locks. Problem is that\nlock_wait_timeout_thread() doesn't remove the table lock from\ntable_locks for transaction.\n\nSolution:\n========\n  In lock_wait_timeout_thread(), remove the lock from table vector of\ntransaction.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/fb3e3a6a3d165d79331f7f359e9c1f28a332c772"},{"sha":"708f1e341915b9fe2968581c60fb6a224b185af9","author":{"name":"Thirunarayanan Balathandayuthapani","email":"eeee3294f1327533d6d73c46ed1259dedcb2c099@mariadb.com"},"message":"MDEV-19647 Server hangs after dropping full text indexes and restart\n\n- There is no need to add the table in fts_optimize_wq if there is\nno fts indexes associated with it.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/708f1e341915b9fe2968581c60fb6a224b185af9"},{"sha":"c471bfb34e970075d8649247ab088b19a097eaf4","author":{"name":"Varun Gupta","email":"6d5ded54c44066f2065003e9f3a7a14b6d8996de@mariadb.com"},"message":"Fixing a test to reset to original state","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/c471bfb34e970075d8649247ab088b19a097eaf4"},{"sha":"8a79fa0e4d0385818da056f7a4a39fde95d62fe3","author":{"name":"Thirunarayanan Balathandayuthapani","email":"eeee3294f1327533d6d73c46ed1259dedcb2c099@mariadb.com"},"message":"MDEV-19529\tInnoDB hang on DROP FULLTEXT INDEX\n\nProblem:\n=======\n  During dropping of fts index, InnoDB waits for fts_optimize_remove_table()\nand it holds dict_sys->mutex and dict_operaiton_lock even though the\ntable id is not present in the queue. But fts_optimize_thread does wait\nfor dict_sys->mutex to process the unrelated table id from the slot.\n\nSolution:\n========\n  Whenever table is added to fts_optimize_wq, update the fts_status\nof in-memory fts subsystem to TABLE_IN_QUEUE. Whenever drop index\nwants to remove table from the queue, it can check the fts_status\nto decide whether it should send the MSG_DELETE_TABLE to the queue.\n\nRemoved the following functions because these are all deadcode.\ndict_table_wait_for_bg_threads_to_exit(),\nfts_wait_for_background_thread_to_start(),fts_start_shutdown(), fts_shudown().","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/8a79fa0e4d0385818da056f7a4a39fde95d62fe3"},{"sha":"13c2fd36c18cbd23ae33bba538982ebceae04ac6","author":{"name":"Otto Kekäläinen","email":"902287fd106bdc113344bdf7dbeb396c4c387b6b@kekalainen.net"},"message":"Deb: Implement proper version detection in maintainer scripts\n\nFixes bug introduced in commit 5415002.\n\nUsing script run-time filename does not always work. One cannot assume\nthat the filename is always the same as there might be temporary file\nnames used by dpkg in certain situations. See Debian #920415.\n\nThe same fix has been successfully in use in Debian official packages\nsince February 2019:\nhttps://salsa.debian.org/mariadb-team/mariadb-10.3/commit/6440c0d6e75","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/13c2fd36c18cbd23ae33bba538982ebceae04ac6"}]}
{"actor":{"display_login":"robertbindar"}}