{"push_id":1456186815,"size":159,"distinct_size":74,"ref":"refs/heads/bb-10.1-wlad-xtrabackup","head":"d71e002a0330287f542b04e82fff0d0f79073f70","before":"ddc7299e9bb1baa99001adab9583f337fab18d84","commits":[{"sha":"aec43216c834c2156e9aca7b7dc182fbdd1916de","author":{"name":"Vladislav Vaintroub","email":"1b9bbb14d1453450ccb1916eb56bca02cf7bb475@mariadb.com"},"message":"MDEV-9409 Windows - workaround VS2015 CRT bug that makes\nmysqldump/mysql_install_db.exe fail\n\nThe bug is described in\nhttps://connect.microsoft.com/VisualStudio/Feedback/Details/1902345\n\nWhen reading from a pipe in text mode, using CRT function such as fread(),\nsome newlines may be lost. Workaround is to use binary mode on reading side\nand if necessary, replace \\r\\n with \\n.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/aec43216c834c2156e9aca7b7dc182fbdd1916de"},{"sha":"d8cb6822bc7deecba26021368c2f08fa6bf59e58","author":{"name":"Vladislav Vaintroub","email":"1b9bbb14d1453450ccb1916eb56bca02cf7bb475@mariadb.com"},"message":"VS2015 build fixes\n\n- new location of signtool\n- silence a nonsensical warning from stl  header\n(complain about noexcept() function attribute, if /EHsc is not set)","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/d8cb6822bc7deecba26021368c2f08fa6bf59e58"},{"sha":"2a2e79b702b28149c8f9984d24367fe3ad7afa13","author":{"name":"Vladislav Vaintroub","email":"1b9bbb14d1453450ccb1916eb56bca02cf7bb475@mariadb.com"},"message":"MDEV-11157 Windows - Upgrade installer to use HeidiSQL 9.4","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/2a2e79b702b28149c8f9984d24367fe3ad7afa13"},{"sha":"cb7b03b00d9b19dbb3ca00947c6e7637917c4e5a","author":{"name":"Sergey Vojtovich","email":"f7bb3c4d1423048768491a0d16a8f7427983335b@mariadb.org"},"message":"MDEV-11164 - hardening-wrapper has been removed from Debian Sid\n\nThe hardening-wrapper package has been removed from Debian Sid. Remove\ndependency and relevant settings.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/cb7b03b00d9b19dbb3ca00947c6e7637917c4e5a"},{"sha":"425d341b980e412d5083056da7b017fbc8bb02e2","author":{"name":"Daniel Bartholomew","email":"a12139f7c9cc1f3eb4b40ca36318a3085c27d596@dbart.us"},"message":"bump the VERSION","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/425d341b980e412d5083056da7b017fbc8bb02e2"},{"sha":"923a7f8675e262b45ee63bffb617477ca5b5011d","author":{"name":"Jan Lindström","email":"89a73df2209a6621e85f6f815b20ae4aa5543013@mariadb.com"},"message":"MDEV-11188: rpl.rpl_parallel_partition fails with valgrind warnings in buildbot and outside","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/923a7f8675e262b45ee63bffb617477ca5b5011d"},{"sha":"9741e0ea7250ef088b29294049902c7f568ba3f5","author":{"name":"Jan Lindström","email":"89a73df2209a6621e85f6f815b20ae4aa5543013@mariadb.com"},"message":"Initialize zip_dict_ids table and avoid referencing array items\nas currently MariaDB does not support compressed columns.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/9741e0ea7250ef088b29294049902c7f568ba3f5"},{"sha":"e0f48e5ce9e77711f6d8cc1397bc32e0bd3edc33","author":{"name":"Vladislav Vaintroub","email":"1b9bbb14d1453450ccb1916eb56bca02cf7bb475@mariadb.com"},"message":"MDEV-11214  Windows : MSI installation fails, if run by a service user (e.g LocalSystem)\n\nSkip  permission for data directory for LogonUser, if installation\nruns by one of the service accounts (determined from their well-known SID).\nThere is no real LogonUser in this case.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/e0f48e5ce9e77711f6d8cc1397bc32e0bd3edc33"},{"sha":"1d9b043a1f5db7ff229d5200652cff7a78ea6266","author":{"name":"Alexander Barkov","email":"0f6b97dba78ece845922cd8b90dcd7bb4ae5b838@mariadb.org"},"message":"A join patch for MDEV-10780 and MDEV-11265\n\nMDEV-10780 Server crashes in in create_tmp_table\nMDEV-11265 Access defied when CREATE VIIEW v1 AS SELECT DEFAULT(column) FROM t1\n\nItem_default_value and Item_insert_value erroneously derive from Item_field\nbut forgot to override some methods that apply only to true fields,\nso the server code mixes Item_{default|insert}_value instances with real\ntable fields (i.e. true Item_field) in some cases.\nOverriding a few methods to avoid this.\n\nTODO: we should eventually derive Item_default_value (and Item_insert_value)\ndirectly from Item, as they don't really need the entire Item_field,\nItem_ident and Item_result_field functionality.\nOnly the member \"Field *field\" related functionality is actually needed,\nlike val_xxx(), is_null(), get_geometry_type(), charset_for_protocol(), etc.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/1d9b043a1f5db7ff229d5200652cff7a78ea6266"},{"sha":"10aee66896a127da599a91f389820937cb4ba832","author":{"name":"Vladislav Vaintroub","email":"1b9bbb14d1453450ccb1916eb56bca02cf7bb475@mariadb.com"},"message":"MDEV-11248 Fix passing offset parameter to my_file_pread in read_ddl_log_file_entry","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/10aee66896a127da599a91f389820937cb4ba832"},{"sha":"96b62b55149a9297f32c3aad99ece613cc3f788f","author":{"name":"Igor Babaev","email":"3b85b3e83e658d5d33308486a92b220edc8ae0a6@askmonty.org"},"message":"Fixed bug mdev-11161.\nThe flag TABLE_LIST::fill_me must be reset to false at the prepare\nphase for any materialized derived table used in the executed query.\nOtherwise if the optimizer decides to generate a key for such a table\nit is generated only for the first execution of the query.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/96b62b55149a9297f32c3aad99ece613cc3f788f"},{"sha":"adc38ed81140701f89b40b3356b5fb7f9587c2b7","author":{"name":"Vladislav Vaintroub","email":"1b9bbb14d1453450ccb1916eb56bca02cf7bb475@mariadb.com"},"message":"Restore MY_WME flag for my_pread in read_ddl_log_entry, fix errors in buildbot","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/adc38ed81140701f89b40b3356b5fb7f9587c2b7"},{"sha":"9a090728805720fb10697267531235cfbac651f4","author":{"name":"Kristian Nielsen","email":"8b2be8e5a84037ac3c98656d8df5dc47c892e72f@knielsen-hq.org"},"message":"Merge branch 'mdev10863' into 10.0","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/9a090728805720fb10697267531235cfbac651f4"},{"sha":"f1fcc1fc105ad0e329b8f6dd11923f99d6edd42b","author":{"name":"Kristian Nielsen","email":"8b2be8e5a84037ac3c98656d8df5dc47c892e72f@knielsen-hq.org"},"message":"Back-port Master_info::using_parallel() to 10.0.\n\nThis has no functional changes, but it helps avoid merge problems from 10.0\nto 10.1. In 10.0, code that checks for parallel replication uses\nopt_slave_parallel_threads > 0, but this check needs to be\nmi->using_parallel() in 10.1. By using the same check in 10.0 (with\nunchanged semantics), merge problems to 10.1 are avoided.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/f1fcc1fc105ad0e329b8f6dd11923f99d6edd42b"},{"sha":"390f2a013b1b223bdce2cd9011a799131eaf13ce","author":{"name":"Kristian Nielsen","email":"8b2be8e5a84037ac3c98656d8df5dc47c892e72f@knielsen-hq.org"},"message":"Fix incorrect reading of events from relaylog in parallel replication.\n\nThe SQL thread keeps track of the position in the current relay log from\nwhich to read the next event. This position is not normally used, but a\ncertain interaction with the IO thread can cause the SQL thread to re-open\nthe relay log and seek to the stored position.\n\nIn parallel replication, there were a couple of places where the position\nwas not updated. This created a race where a re-open of the relay log could\nseek to the wrong position and start re-reading and processing events\nalready handled once, causing various kinds of problems.\n\nFix this by moving the position update into a single place in\napply_event_and_update_pos(), which should ensure that the position is\nalways updated in the parallel replication case.\n\nThis problem was found from the testcase of MDEV-10863, but it is logically\na separate problem.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/390f2a013b1b223bdce2cd9011a799131eaf13ce"},{"sha":"42a398b59b5c2d08a9cc8c03d6d082a095a2cd77","author":{"name":"Alexander Barkov","email":"0f6b97dba78ece845922cd8b90dcd7bb4ae5b838@mariadb.org"},"message":"Fixing a typo in the patch for MDEV-10780, which caused default.test failure.\n\nFixing the \"connect\" command to use \"localhost\" instead of \"127.0.0.1\"\nto make it work with both \"mtr\" and \"mtr --embedded\".","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/42a398b59b5c2d08a9cc8c03d6d082a095a2cd77"},{"sha":"03ddc19ab21d585f4aac16ad91e5cba39687cd31","author":{"name":"Jan Lindström","email":"89a73df2209a6621e85f6f815b20ae4aa5543013@mariadb.com"},"message":"MDEV-6424: MariaDB server crashes with assertion failure in file ha_innodb.c line 11652\n\nThis is not a fix, this is instrumentation to find out is MySQL frm dictionary\nand InnoDB data dictionary really out-of-sync when this assertion is fired,\nor is there some other reason (bug).","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/03ddc19ab21d585f4aac16ad91e5cba39687cd31"},{"sha":"d145d1b6ee42ffa7f9ca2ce02478a31a09f3fe99","author":{"name":"Kristian Nielsen","email":"8b2be8e5a84037ac3c98656d8df5dc47c892e72f@knielsen-hq.org"},"message":"fix bogus stalls in the lock tree for low concurrency applications\n\nMerge into the MariaDB tree the pull request from Rich Prohaska for\nPerconaFT. These changes are needed to get parallel replication to\nwork with TokuDB. Once the pull request is accepted by Percona and the new upstream version enters MariaDB, this commit can be superseded.\n\nOriginal commit message from Rich Prohaska:\n\n    1. Fix the release before wait race\n\n    The release before wait race occurs when a lock is released by transaction A after transaction B tried to acquire it but before transaction B has a chance to register it's pending lock request.  There are several ways to fix this problem, but we want to optimize for the common situation of minimal lock conflicts, which is what the lock acquisition algorithm currently does.  Our solution to the release before wait race is for transaction B to retry its lock request after its lock request has been added to the pending lock set.\n\n    2. Fix the retry race\n\n    The retry race occurs in the current lock retry algorithm which assumes that if some transaction is running lock retry, then my transaction does not also need to run it.  There is a chance that some pending lock requests will be skipped, but these lock requests will eventually time out.  For applications with small numbers of concurrent transactions, timeouts will frequently occur, and the application throughput will be very small.\n\n    The solution to the retry race is to use a group retry algorithm.  All threads run through the retry logic.  Sequence numbers are used to group retries into batches such that one transaction can run the retry logic on behalf of several transactions.  This amortizes the retry cost.  The sequence numbers also ensure that when a transaction releases its locks, all of the pending lock requests that it is blocking are retried.\n\n    3. Implement a mechanism to find and kill a pending lock request\n\n    Tags lock requests with a client id, use the client id as a key into the pending lock requests sets to find a lock request, complete the lock request with a lock timeout error.\n\n    Copyright (c) 2016, Rich Prohaska\n    All rights reserved.\n\n    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:\n\n    1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.\n\n    2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.\n\n    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/d145d1b6ee42ffa7f9ca2ce02478a31a09f3fe99"},{"sha":"660a2928a535e36e5dda846677dce4ba96508cd7","author":{"name":"Kristian Nielsen","email":"8b2be8e5a84037ac3c98656d8df5dc47c892e72f@knielsen-hq.org"},"message":"Fix optimistic parallel replication for TokuDB.\n\nMake TokuDB report row lock waits with thd_rpl_deadlock_check(). This allows\nparallel replication to properly detect conflicts, and kill and retry the\noffending transaction.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/660a2928a535e36e5dda846677dce4ba96508cd7"},{"sha":"021f78f6956d2f33cfbee3b3a2a20e9c822e0c98","author":{"name":"Kristian Nielsen","email":"8b2be8e5a84037ac3c98656d8df5dc47c892e72f@knielsen-hq.org"},"message":"Use thd_kill_level() over old thd_killed() in TokuDB.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/021f78f6956d2f33cfbee3b3a2a20e9c822e0c98"}]}
{"actor":{"display_login":"vaintroub"}}