{"push_id":1299664237,"size":36,"distinct_size":1,"ref":"refs/heads/bug1619559-5.7","head":"79f180fe2a6851f68cadd0616f88a30ce03074a9","before":"4ffafeedf3f2bdca9240d479e46e94fb83a6e0f8","commits":[{"sha":"2e0c5e056d83d7dcb9b9cfc644bbeb9e7a482da7","author":{"name":"Sergei Glushchenko","email":"96a2e2d871a5be68c2cae8915fd63293286a504b@gmail.com"},"message":"Bug 1617833: audit_log_default_db failures\n\n1. Insert silent statement after UNINSTALL PLUGIN to make sure that SHOW\n   WARNINGS is logged before the statement from the next connection.\n\n2. Insert silent statement before establishing the connection which does\n   'INSTALL PLUGIN', make sure 'SELECT * FROM t' gets to the log.\n\n3. Make reconnect in case of error optional for 'change_user' mysqltest\n   command","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/2e0c5e056d83d7dcb9b9cfc644bbeb9e7a482da7"},{"sha":"6450196633329e61075a842cce1d61a54c7848df","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Fix bug 1621012 / 82886 (Server may crash due to a glibc bug in handling short-lived detached threads)\n\nGlibc is affected by a bug where a short-lived detached thread, that\nmanages to complete before the caller thread finishes executing\npthread_create, may crash server. In MySQL, at least the InnoDB full\ntext parallel merge threads might be short-lived enough to hit this.\n\nImplement a workaround to join these threads instead of detaching\nthem.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/6450196633329e61075a842cce1d61a54c7848df"},{"sha":"ab28cbcf35126d84a758faeb1bf9d584097f6e0f","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Backport fixes for bug 1621046 / 45679 (KILL QUERY not behaving consistently and will hang in some cases)\n\nBackported commits:\n\ncommit 1ff551ee095c6abbb89e8185063c033d6f49c349\nAuthor: Raghav Kapoor <raghav.kapoor@oracle.com>\nDate:   Mon Feb 25 14:07:35 2013 +0530\n\n    BUG#11790057 KILL QUERY WILL AFFECT THE NEXT COMMAND INCORRECTLY\n    Bug#11754124:KILL QUERY NOT BEHAVING CONSISTENTLY AND WILL HANG IN SOME CASES\n\n    BACKGROUND OF BUG#11790057\n    SCENARIO 1:\n    When a very long SELECT is running in one connection and it\n    is just flushing its output on the console and, In another\n    connection a KILL QUERY command is issued, the next query\n    executed in the first connection would throw\n    ER_QUERY_INTERRUPTED which is wrong.\n\n    SCENARIO 2:\n    When an INSERT query is running in one connection and it is\n    in final stage to commit itself by acquiring MDL locks and\n    waiting for the lock (i.e it is blocked because Flush Tables\n    With Read Lock (FTWRL) is issued in another connection) and,\n    In another connection, a KILL QUERY command is issued to kill\n    that blocked INSERT query, it would not result a Query\n    Interrupted Error.\n    Rather the next query issued after INSERT in the connection\n    would throw error ER_QUERY_INTERRUPTED.\n    This behaviour is wrong.\n\n    ANALYSIS OF BUG#11790057:\n    SCENARIO 1:\n    In this scenario, SELECT has cleared all the stages and it is\n    just flushing its output on the console through send() system\n    call which is non blocking.\n    Here if a user issues kill query in another connection,\n    in the kill reception code there was no check to determine if\n    the command is finished executing and it should not set the kill\n    flag for that thread.\n\n    SCENARIO 2:\n    The state of blocked INSERT query is set to MDL_wait::KILLED due\n    to KILL QUERY being issued in another session. No error was thrown.\n    The state of INSERT executing thread would be set to THD::KILL_QUERY\n    by kill reception code and it would affect the next command incorrectly.\n\n    FIX FOR BUG#11790057:\n    SCENARIO 1:\n    A check has been added in the kill reception code that if any\n    kill request comes in after the command is processed but\n    before the next command is received, it should not set the kill\n    flag for that thread because there is no active command being\n    processed.\n    SCENARIO 2:\n    When the query waiting on MDL Lock is killed, its state is set to\n    MDL_WAIT::KILLED. As a fix, an error ER_QUERY_INTERRUPTED is thrown\n    from there.\n    After the error is thrown from inside trans_commit_stmt() function,\n    the thread state is reset to NOT_KILLED, by rearranging the code\n    inside if (!thd->sub_stmt) so that next command does not get affected.\n\n    BACKGROUND OF BUG#11754124:\n    This bug is pretty similar or we can say duplicate of Bug#11790057,\n    Only difference is more number of scenarios of unexpected behaviour\n    of KILL QUERY are presented in this bug than Bug#11790057, and they\n    are pretty much clear from the bug description.\n\n    ANALYSIS OF BUG#11754124:\n    All the scenarios mentioned in this bug are already been taken care\n    by the patch submitted for Bug#11790057. Only Additional test cases\n    are written to test the scenarios mentioned in this bug.\n    DETAILED ANALYSIS OF SCENARIOS:\n    1. Scenario 1, 2, 4 and 8 mentioned in the bug report are reproducible\n       and are fixed with the current patch.\n    2. Scenario 3 is Reproducible in 5.1. It is not reproducible in 5.5,\n       5.6 and trunk.\n       The above scenarios 1, 2, 4 and 8 were fixed by the check\n       added in sql_kill() function submitted as a patch for\n       Scenario 1 of Bug#11790057.\n    3. Scenario 5, 6, 7 are not reproducible as they are\n       described in the bug report in any of the versions.\n       When we CALL a successfully created stored procedure, and a\n       KILL QUERY is issued before in another session, the CALL to\n       stored procedure terminates with ER_QUERY_INTERRUPTED error.\n       After that if we again CALL it, it works fine.\n       The above is applicable to Scenarios 5, 6 and 7 mentioned\n       in the bug report.\n       Scenario 9 is special because here KILL is issued concurrently\n       when we are calling the stored procedure.\n       For Scenario 9 there are two cases:\n       CASE 1:\n       A SELECT SLEEP(10) query is present inside a stored procedure\n       and a handler is declared for it. In this case, When we do KILL\n       when the sleep is executing, it goes to  pthread_cond_timedwait()\n       system call. This system call does not return an error code of EINTR,\n       when it is killed. The system call passes and only the state of\n       thread is set to KILL_QUERY.\n       Since there is no error generated by the SLEEP(10), handler does not\n       get activated in any of the versions. This behaviour is present in all\n       the versions starting from 5.1 and is correct.\n       CASE 2:\n       A very long running SELECT query is present inside a Stored Procedure\n       and a handler is declared for it. In 5.1, CONTINUE handler for this is\n       executed when a FATAL error happens which should not be the behaviour.\n       See Bug #15192 for more details.\n       In 5.5, 5.6 and trunk, handler for this is not executed since it is a\n       FATAL error. Therefore, this behaviour is correct.\n\n    FIX FOR BUG#11754124:\n    The fix for this bug is same as the patch submitted for Bug#11790057.\n    Additional test coverage is submitted as patch for this bug.\n\ncommit 33eba69e9f7732e0f16e6b6a1f40b39287f0721c\nAuthor: Raghav Kapoor <raghav.kapoor@oracle.com>\nDate:   Sun Mar 10 15:42:52 2013 +0530\n\n    BUG#16457803 - MAIN.SHOW_CHECK UNSTABLE ON PB2\n\n    BACKGROUND:\n    After fix for Bug#11754124, main.show_check starts failing\n    occasionally on pb2.\n\n    FIX:\n    Submitted the patch to make the test case more robust.\n\ncommit 3f5ccb3f28443334ef2ab957490e4750de6954c5\nAuthor: Raghav Kapoor <raghav.kapoor@oracle.com>\nDate:   Tue Apr 9 17:12:15 2013 +0530\n\n    BUG#16457803 - MAIN.SHOW_CHECK UNSTABLE ON PB2\n\n    BACKGROUND:\n    After fix for Bug#11754124, main.show_check starts failing\n    occasionally on pb2 under high load.\n\n    FIX:\n    Submitted the patch by to make the test case more robust.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/ab28cbcf35126d84a758faeb1bf9d584097f6e0f"},{"sha":"e19bb630304a14393fb832c343ce4c0cf1b5ae63","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge branch 'bug1621046-5.6' into bug1621046-5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/e19bb630304a14393fb832c343ce4c0cf1b5ae63"},{"sha":"05a0358a5ab469e1c8a3009be848a15e9587ef23","author":{"name":"Evgeniy Patlan","email":"5857cf11066ae34d18259462f004db12293a3e09@percona.com"},"message":"my.cnf should be provided on all distros.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/05a0358a5ab469e1c8a3009be848a15e9587ef23"},{"sha":"7c91ad4b89dd4bb7e2a748992b2b2f038dfdaab3","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge branch 'bug1621012-5.6' into bug1621012-5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/7c91ad4b89dd4bb7e2a748992b2b2f038dfdaab3"},{"sha":"8f90efee0c2fb9fcb1a66c8c76a4774ad4e93f0c","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Work towards diagnosing bug 1621060 (Test innodb.innodb_stats_auto_recals fails intermittently)\n\nReplace \"die\" with \"echo\" in mysql-test/include/wait_condition.inc in\ncase of failure to allow the testcase to proceed and show the result\ndiff. This also makes this include file consistent with both 5.5 and\n5.7.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/8f90efee0c2fb9fcb1a66c8c76a4774ad4e93f0c"},{"sha":"8d9fc857d7e214113d26a2c02352a26355472289","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge branch 'bug1621060-diag-5.6' into bug1621060-diag-5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/8d9fc857d7e214113d26a2c02352a26355472289"},{"sha":"992c956b73c009fb760263d6e73e20857563f543","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge pull request #987 from laurynas-biveinis/bug1621046-5.7\n\nBug1621046 5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/992c956b73c009fb760263d6e73e20857563f543"},{"sha":"0fce43612bffa8beb3c54931236f10273c7e7aad","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge pull request #989 from laurynas-biveinis/bug1621012-5.7\n\nBug1621012 5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/0fce43612bffa8beb3c54931236f10273c7e7aad"},{"sha":"e242f97b9fa97bce516da2d57ba6c8c02ca83020","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge pull request #991 from laurynas-biveinis/bug1621060-diag-5.7\n\nBug1621060 diag 5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/e242f97b9fa97bce516da2d57ba6c8c02ca83020"},{"sha":"a25eb8a90e4df6e5b608175a951ebc47e72c0186","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Fix bug 1622449 (Test innodb.innodb_replace is unstable)\n\nPrevent INSERT on con1 overtaking SELECT LOCK IN SHARE MODE on the\ndefault connection by reaping its query first.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/a25eb8a90e4df6e5b608175a951ebc47e72c0186"},{"sha":"e395886d5eda4b30ac7aa49d37e73782a81fc3b9","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge branch 'bug1622449-5.6' into bug1622449-5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/e395886d5eda4b30ac7aa49d37e73782a81fc3b9"},{"sha":"05846d3dc7bf35e41ed6aeeda5d007a54084d7e6","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Fix bug 1622456 (Test main.mysql_client_test fails testcase check intermittently)\n\nWait for connections opened by mysql_client_test to close.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/05846d3dc7bf35e41ed6aeeda5d007a54084d7e6"},{"sha":"400dfcbc4f8af888a154ff8983dc1a1fd4a0b6cf","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge branch 'bug1622456-5.6' into bug1622456-5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/400dfcbc4f8af888a154ff8983dc1a1fd4a0b6cf"},{"sha":"84bc0d6c1c835b46697d9b3e5b973cd6d269019b","author":{"name":"EvgeniyPatlan","email":"5857cf11066ae34d18259462f004db12293a3e09@percona.com"},"message":"Merge pull request #907 from EvgeniyPatlan/provide_my_cnf\n\nmy.cnf should be provided on all distros.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/84bc0d6c1c835b46697d9b3e5b973cd6d269019b"},{"sha":"0685201a2fbcb184cfd8fedf207aa4b4e8fb9f38","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge pull request #995 from laurynas-biveinis/bug1622449-5.7\n\nBug1622449 5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/0685201a2fbcb184cfd8fedf207aa4b4e8fb9f38"},{"sha":"1739f7680c6eb412529a9182c9c52e3ffd5fe20d","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge pull request #997 from laurynas-biveinis/bug1622456-5.7\n\nBug1622456 5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/1739f7680c6eb412529a9182c9c52e3ffd5fe20d"},{"sha":"b160802139d13cd481299e95af65c86cfb8546c1","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Add asserts to catch bug 1622868 (LSN rolls back by 10 on shutdown intermittently)\n\nSpecifically, assert that\n- next checkpoint LSN only advances forward, both in log_sys and in\nlog file;\n- no checkpoints happen at the very last phase of InnoDB shutdown;\n- last_checkpoint_lsn does not move during the same phase.","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/b160802139d13cd481299e95af65c86cfb8546c1"},{"sha":"742884106e5dc0d1cbe28454d8d51c193d67eb33","author":{"name":"Laurynas Biveinis","email":"00d65ad0601c13a1f9a943b6a7d33d774ecc4531@gmail.com"},"message":"Merge branch 'bug1622868-5.6' into bug1622868-5.7","distinct":false,"url":"https://api.github.com/repos/laurynas-biveinis/percona-server/commits/742884106e5dc0d1cbe28454d8d51c193d67eb33"}]}
{"actor":{"display_login":"laurynas-biveinis"}}