{"push_id":2639356737,"size":7,"distinct_size":1,"ref":"refs/heads/bb-10.1-andrei","head":"c7a2d42c30b9c4b807ef661b44c733e4a111f348","before":"828770eb23ecabed503a8e3bc61f272914093926","commits":[{"sha":"55abcfa7b70968246a1a26a8839013ebb8f5c506","author":{"name":"Marko Mäkelä","email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@mariadb.com"},"message":"MDEV-16124 fil_rename_tablespace() times out and crashes server during table-rebuilding ALTER TABLE\n\nInnoDB insisted on closing the file handle before renaming a file.\nRenaming a file should never be a problem on POSIX systems. Also on\nWindows it should work if the file was opened in FILE_SHARE_DELETE\nmode.\n\nfil_space_t::stop_ios: Remove. We no longer need to stop file access\nduring rename operations.\n\nfil_mutex_enter_and_prepare_for_io(): Remove the wait for stop_ios.\n\nfil_rename_tablespace(): Remove the retry logic; do not close the\nfile handle. Remove the unused fault injection that was added along\nwith the DATA DIRECTORY functionality (MySQL WL#5980).\n\nos_file_create_simple_func(), os_file_create_func(),\nos_file_create_simple_no_error_handling_func(): Include FILE_SHARE_DELETE\nin the share_mode. (We will still prevent multiple InnoDB instances\nfrom using the same files by not setting FILE_SHARE_WRITE.)","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/55abcfa7b70968246a1a26a8839013ebb8f5c506"},{"sha":"1d4e1d3263bf3b87b473c12d4876f368dc3450b6","author":{"name":"Marko Mäkelä","email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@mariadb.com"},"message":"Merge 10.0 to 10.1","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/1d4e1d3263bf3b87b473c12d4876f368dc3450b6"},{"sha":"3627dd7f6a1cf5bd7151ff23290d64cb6dffea90","author":{"name":"Marko Mäkelä","email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@mariadb.com"},"message":"MDEV-16416 Crash on IMPORT TABLESPACE of a ROW_FORMAT=COMPRESSED table\n\nfil_iterate(): Invoke fil_encrypt_buf() correctly when\na ROW_FORMAT=COMPRESSED table with a physical page size of\ninnodb_page_size is being imported. Also, validate the page checksum\nbefore decryption, and reduce the scope of some variables.\n\nAbstractCallback::operator()(): Remove the parameter 'offset'.\nThe check for it in FetchIndexRootPages::operator() was basically\nredundant and dead code since the previous refactoring.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/3627dd7f6a1cf5bd7151ff23290d64cb6dffea90"},{"sha":"c17468d4abe59339af11ef4a17a59156741c6a21","author":{"name":"Varun Gupta","email":"0eaaf020e24ab2e5cb333952982b7688b3b4d3b1@gmail.com"},"message":"MDEV-16191: Analyze format=json gives incorrect value for r_limit inside a dependent\nsubquery when ORDER BY is present\n\nCurrently for setting r_limit we divide with the number of iterations we invoke the dependent subquery.\nThis is not needed for the case of limit. For varying limits we produce the output that the limit varies with\nexecution.\nAlso there is a type for filtered , we forgot to multiply by 100 as it is represented as a percent.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/c17468d4abe59339af11ef4a17a59156741c6a21"},{"sha":"5227198908d4f12ab3e5c95e4c8f15e6b9805f10","author":{"name":"Alexander Barkov","email":"62cdb7020ff920e5aa642c3d4066950dd1f01f4d@mariadb.com"},"message":"MDEV-16190 Server crashes in Item_null_result::field_type on SELECT with time field, ROLLUP and HAVING\n\nvirtual Item_null_result::get_date() was not overridden.\nIt used the inherited Item::get_date(), which tests field_type(),\nwhich in case of Item_null_result calls result_field->field_type(),\nand result_field is not really always set (e.g. it's not set in the\ntest case from the bug report).\n\nOverriding Item_null::get_date() like it's done for other val_xxx() methods.\nThis make the code more symmetric across data types.\n\nIn the new reduction, get_date() immediately returns NULL without entering\ninto any data type specific code.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/5227198908d4f12ab3e5c95e4c8f15e6b9805f10"},{"sha":"26be5072429082e634b8fc102609370975443439","author":{"name":"Alexander Barkov","email":"62cdb7020ff920e5aa642c3d4066950dd1f01f4d@mariadb.com"},"message":"MDEV-12060 Crash in EXECUTE IMMEDIATE with an expression returning a GRANT command\n\nBackporting (partially) the fix for MDEV-14603.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/26be5072429082e634b8fc102609370975443439"},{"sha":"c7a2d42c30b9c4b807ef661b44c733e4a111f348","author":{"name":"Andrei Elkin","email":"f97f40c773a644e49b3e8fb34ba7ac6ad4c1f7e1@mariadb.com"},"message":"MDEV-14014 Multi-Slave Replication Fail: bogus data in log event\n\nMDEV-7257 made a dump thread to read from binlog concurrently with\nwriters as long as the read bytes are below a water-mark\n(MYSQL_BIN_LOG::binlog_end_pos). However it appeared to be possible a\ndump thread reader reach out for bytes past the water mark through a\nfeature of IO_CACHE that fills in the internal buffer and while doing\nso it could read what the reader is not supposed to see (the bytes\nabove MYSQL_BIN_LOG::binlog_end_pos).\n\nThe issue is fixed with constraining the IO_CACHE buffer fill to respect\nthe watermark.\nAn added test simulates potentially unconstrained buffer fill and an\nassert guards this is not the case anymore.","distinct":true,"url":"https://api.github.com/repos/MariaDB/server/commits/c7a2d42c30b9c4b807ef661b44c733e4a111f348"}]}
{"actor":{"display_login":"andrelkin"}}