{"push_id":783391831,"size":36,"distinct_size":35,"ref":"refs/heads/5.5","head":"8db38198c08d18b965962eadab151b40274cd465","before":"bff725a3b61de0e58e09abbe0c30e1239c477999","commits":[{"sha":"f5ac718b1db7a012d113b051ef74932c6e0a29df","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"Raise version number after cloning 5.5.44","distinct":false,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/f5ac718b1db7a012d113b051ef74932c6e0a29df"},{"sha":"e7b6e814bea7a9e21ef864016bde39fd65a7f655","author":{"email":"3dd7fa59519d1d3dbf7043cc4f1397eca520ea4c@oracle.com","name":"Annamalai Gurusami"},"message":"Bug #19138298 RECORD IN INDEX WAS NOT FOUND ON ROLLBACK, TRYING TO INSERT\n\nScenario:\n\n1. The purge thread takes an undo log record and parses it and forms\n   the record to be purged. We have the primary and secondary keys\n   to locate the actual records.\n2. Using the secondary index key, we search in the secondary index.\n   One record is found.\n3. Then it is checked if this record can be purged.  The answer is we\n   can purge this record.  To determine this we look up the clustered\n   index record.  Either there is no corresponding clustered index\n   record, or the matching clustered index record is delete marked.\n4. Then we check whether the secondary index record is delete marked.\n   We find that it is not delete marked.  We report warning in optimized\n   build and assert in debug build.\n\nProblem:\n\nIn step 3, we report that the record is purgeable even though it is\nnot delete marked.  This is because of inconsistency between the\nfollowing members of purge_node_t structure - found_clust, ref and pcur.\n\nSolution:\n\nIn the row_purge_reposition_pcur(), if the persistent cursor restore\nfails, then reset the purge_node_t->found_clust member.  This will\nkeep the members of purge_node_t structure in a consistent state.\n\nrb#8813 approved by Marko.","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/e7b6e814bea7a9e21ef864016bde39fd65a7f655"},{"sha":"515b2203c5913679757fa2cf39f017001f7e29ee","author":{"email":"cf76068089fe2168a7cd73d620466fc868c313f4@oracle.com","name":"Ajo Robert"},"message":"Bug #18075170 SQL NODE RESTART REQUIRED TO\nAVOID DEADLOCK AFTER RESTORE\n\nAnalysis\n--------\nAccessing the restored NDB table in an active multi-statement\ntransaction was resulting in deadlock found error.\n\nMySQL Server needs to discover metadata of NDB table from\ndata nodes after table is restored from backup. Metadata\ndiscovery happens on the first access to restored table.\nCurrent code mandates this statement to be the first one\nin the transaction. This is because discover needs exclusive\nmetadata lock on the table. Lock upgrade at this point can\nlead to MDL deadlock and the code was written at the time\nwhen MDL deadlock detector was not present. In case when\ndiscovery attempted in the statement other than the first\none in transaction ER_LOCK_DEADLOCK error is reported\npessimistically.\n\nFix:\n---\nRemoved the constraint as any potential deadlock will be\nhandled by deadlock detector. Also changed code in discover\nto keep metadata locks of active transaction.\n\nSame issue was present in table auto repair scenario. Same\nfix is added in repair path also.","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/515b2203c5913679757fa2cf39f017001f7e29ee"},{"sha":"820bf7b1f17fbaedb1061c7c845e755e6ebc1572","author":{"email":"cf76068089fe2168a7cd73d620466fc868c313f4@oracle.com","name":"Ajo Robert"},"message":"Bug #18075170 SQL NODE RESTART REQUIRED TO\nAVOID DEADLOCK AFTER RESTORE\n\nTest Failure Fix.","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/820bf7b1f17fbaedb1061c7c845e755e6ebc1572"},{"sha":"dc45e408250c582eb532417a42cef5b5a8e2fe77","author":{"email":"a94b1b24f73207a393ad5259515c15c532c7e2a2@oracle.com","name":"Tatiana Azundris Nuernberg"},"message":"Bug#20642505: HENRY SPENCER REGULAR EXPRESSIONS (REGEX) LIBRARY\n\nThe MySQL server uses Henry Spencer's library for regular\nexpressions to support the REGEXP/RLIKE string operator.\nThis changeset adapts a recent fix from the upstream for\nbetter 32-bit compatiblity. (Note that we cannot simply use\nthe current upstream version as a drop-in replacement\nfor the version used by the server as the latter has\nbeen extended to understand MySQL charsets etc.)","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/dc45e408250c582eb532417a42cef5b5a8e2fe77"},{"sha":"b4daac21f52ced96c11632b83445111c0acede56","author":{"email":"089866e92a65c575b53d5f7e1827581deca50800@oracle.com","name":"Bin Su"},"message":"Bug#21113036 - MYSQL/INNODB MIX BUFFERED AND DIRECT IO\n\nAs man page of open(2) suggested, we should open the same file in the same\nmode, to have better performance. For some data files, we will first call\nos_file_create_simple_no_error_handling_func() to open them, and then call\nos_file_create_func() again. We have to make sure if DIRECT IO is specified,\nthese two functions should both open file with O_DIRECT.\n\nReviewed-by: Sunny Bains <sunny.bains@oracle.com>\nRB: 8981","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/b4daac21f52ced96c11632b83445111c0acede56"},{"sha":"42fab527a7d5d8317035456ef12258e868d2389d","author":{"email":"da39a3ee5e6b4b0d3255bfef95601890afd80709","name":"mysql-builder@oracle.com"},"message":"","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/42fab527a7d5d8317035456ef12258e868d2389d"},{"sha":"c0055f0d41af73f0d8a59ccb66fc7a3a43acdeaa","author":{"email":"d218f434ab5a0a58da5216ac6788f0802d0f8777@oracle.com","name":"Bjorn Munch"},"message":"Raise version number after tagging 5.1.75","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/c0055f0d41af73f0d8a59ccb66fc7a3a43acdeaa"},{"sha":"50be523e06d68feefe48142386b663dba03088c4","author":{"email":"d218f434ab5a0a58da5216ac6788f0802d0f8777@oracle.com","name":"Bjorn Munch"},"message":"Empty version change upmerge","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/50be523e06d68feefe48142386b663dba03088c4"},{"sha":"4b8304a9a41c8382d18e084608c33e5c27bec311","author":{"email":"0af627adff678070af2a3615242f9b46327ff8e8@oracle.com","name":"Debarun Banerjee"},"message":"BUG#21126772 VALGRIND FAILURE IN ENGINES/FUNCS SUITE\n\nProblem :\n---------\nThis is a regression of bug-19138298. During purge, if\nbtr_pcur_restore_position fails, we set found_clust to FALSE\nso that it can find a possible clustered index record in future\ncalls for the same undo entry. This, however, overwrites the\nold_rec_buf while initializing pcur again in next call.\n\nThe leak is reproducible in local environment and with the\ntest provided along with bug-19138298.\n\nSolution :\n----------\nIf btr_pcur_restore_position() fails close the cursor.\n\nReviewed-by: Marko Makela <Marko.Makela@oracle.com>\nReviewed-by: Annamalai Gurusami <Annamalai.Gurusami@oracle.com>\n\nRB: 9074","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/4b8304a9a41c8382d18e084608c33e5c27bec311"},{"sha":"e59914034ab695035c3fe48f046a96bb98d53044","author":{"email":"0af627adff678070af2a3615242f9b46327ff8e8@oracle.com","name":"Debarun Banerjee"},"message":"BUG#21065746 RQG_PARTN_PRUNING_VALGRIND FAILED IN REM0REC.CC\n\nProblem :\n---------\nThis is a regression of Bug#19138298. In purge_node_t::validate_pcur\nwe are trying to get offsets for all columns of clustered index from\nstored record in persistent cursor. This would fail when stored record\nis not having all fields of the index. The stored record stores only\nfields that are needed to uniquely identify the entry.\n\nSolution :\n----------\n1. Use pcur.old_n_fields to get fields that are stored\n2. Add comment to note dependency between stored fields in purge node\nref and stored cursor.\n3. Return if the cursor record is not already stored as it is not safe\nto access cursor record directly without latch.\n\nReviewed-by: Marko Makela <marko.makela@oracle.com>\n\nRB: 9139","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/e59914034ab695035c3fe48f046a96bb98d53044"},{"sha":"044e3b1d07c0854c39178d3054ab0cd0a3188436","author":{"email":"57a9461ad3972b3802cf500c927040dc082abf56@oracle.com","name":"Arun Kuruvila"},"message":"Bug #20605441 : BUFFER OVERFLOW IN MYSQLSLAP\n\nDescription:- mysqlslap is a diagnostic utility designed to\nemulate client load for a MySQL server and to report the\ntiming of each stage. This utility crashes when invalid\nvalues are passed to the options 'num_int_cols_opt' or\n'num_chars_cols_opt' or 'engine'.\n\nAnalysis:- mysqlslap uses \"parse_option()\" to parse the\nvalues specified to the options 'num_int_cols_opt',\n'num_chars_cols_opt' and 'engine'. These options takes\nvalues separated by commas. In \"parse_option()\", the comma\nseparated values are separated and copied into a buffer\nwithout checking the length of the string to be copied. The\nsize of the buffer is defined by a macro HUGE_STRING_LENGTH\nwhose value is 8196. So if the length of the any of the\ncomma separated value exceeds HUGE_STRING_LENGTH, will\nresult in a buffer overflow.\n\nFix:- A check is introduced in \"parse_option()\" to check\nwhether the size of the string to be copied is more than\nHUGE_STRING_LENGTH. If it is more, an error, \"Invalid value\nspecified for the option 'xxx'\" is thrown.\nOption length was incorrectly calculated for the last comma\nseparated value. So fixed that as well.","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/044e3b1d07c0854c39178d3054ab0cd0a3188436"},{"sha":"95cb8c1dd398d33cc41e68f4abe7125f2e3dc018","author":{"email":"57a9461ad3972b3802cf500c927040dc082abf56@oracle.com","name":"Arun Kuruvila"},"message":"Merge branch 'mysql-5.1' into mysql-5.5","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/95cb8c1dd398d33cc41e68f4abe7125f2e3dc018"},{"sha":"e070d1fc80d2c710902782429b52ebfe4407d11b","author":{"email":"da39a3ee5e6b4b0d3255bfef95601890afd80709","name":"mysql-builder@oracle.com"},"message":"","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/e070d1fc80d2c710902782429b52ebfe4407d11b"},{"sha":"3f9bb9194794c85513f45c861abf2dee830164a3","author":{"email":"da39a3ee5e6b4b0d3255bfef95601890afd80709","name":"mysql-builder@oracle.com"},"message":"","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/3f9bb9194794c85513f45c861abf2dee830164a3"},{"sha":"cbf9494e385403171160bc0f81570c1837c7f820","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"Add packaging scripts for docker builds","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/cbf9494e385403171160bc0f81570c1837c7f820"},{"sha":"5768c0adf5f4cbc7036bfc14c81b9732f1c416b1","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"Updated CMakeLists.txt to include rpm-docker directory","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/5768c0adf5f4cbc7036bfc14c81b9732f1c416b1"},{"sha":"bb7951ae9558d1af6ddbae443f215ba7b788414f","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"Bug#21262883 - MYSQL-SYSTEMD-START SCRIPT ERROR WHEN USING OPTION DATADIR OR SIMILAR\n\nFixed the syntax in mysql-systemd-start script","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/bb7951ae9558d1af6ddbae443f215ba7b788414f"},{"sha":"0dedf55d5d12d70f8c81f61ca562b312ae66a9f1","author":{"email":"8991bbd94e79c5e5509ff97a5f2f3e66c1238c76@oracle.com","name":"Tor Didriksen"},"message":"Bug#19660891 HANDLE_FATAL_SIGNAL (SIG=11) IN QUEUE_INSERT\n\nBackport from 5.6 to 5.5\nThis makes filesort robust to misc variants of order by / group by\non columns/expressions with zero length.","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/0dedf55d5d12d70f8c81f61ca562b312ae66a9f1"},{"sha":"dbbe747e54a320d810fff1896ed9e553d43a0bae","author":{"email":"b6aa5ea3ad952b94372dc9c2ad44070433b7508e@oracle.com","name":"V S Murthy Sidagam"},"message":"Bug #21221862 NEWEST RHEL/CENTOS OPENSSL UPDATE BREAKS MYSQL DHE CIPHERS\n\nDescription: The newest RHEL/CentOS/SL 6.6 openssl package\n(1.0.1e-30.el6_6.9; published around 6/4/2015) contains a fix for\nLogJam. RedHat's fix for this was to limit the use\nof any SSL DH key sizes to a minimum of 768 bits. This breaks any\nDHE SSL ciphers for MySQL clients as soon as you install the\nopenssl update, since in vio/viosslfactories.c, the default\nDHPARAM is a 512 bit one. This cannot be changed in\nconfiguration/runtime; and needs a recompile. Because of this the\nclient connection with --ssl-cipher=DHE-RSA-AES256-SHA is not\nable to connect the server.\n\nAnalysis: Openssl has changed Diffie-Hellman key from the 512 to\n1024 due to some reasons(please see the details at\nhttp://openssl.org/news/secadv_20150611.txt) Because of this the client\nwith DHE cipher is failing to connect the server. This change took\nplace from the openssl-1.0.1n onwards.\n\nFix: Similar bug fix is already pushed to mysql-5.7 under bug#18367167.\nHence we backported the same fix to mysql-5.5 and mysql-5.6.","distinct":true,"url":"https://api.github.com/repos/gl-sergei/percona-server/commits/dbbe747e54a320d810fff1896ed9e553d43a0bae"}]}