{"push_id":896105159,"size":33,"distinct_size":1,"ref":"refs/heads/5.5","head":"1a72c6fefdb48642f66dc6f32d8bc7a4cc607437","before":"dac3149f3f3cd79c8b2066f1030782eefb62ad15","commits":[{"sha":"6d30383e78c8b9aba56f645421f437af63706efe","author":{"email":"fd4294049218891e19da8d5f16ff16358147e197@oracle.com","name":"Murthy Narkedimilli"},"message":"Raise version number after cloning 5.5.46","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/6d30383e78c8b9aba56f645421f437af63706efe"},{"sha":"97ea06e807628b6d079ae5f72f5ee0c0ea391caf","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"Raise version number after tagging 5.1.77","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/97ea06e807628b6d079ae5f72f5ee0c0ea391caf"},{"sha":"0bb654b8d9161ecf46684d040c08b86bbc74a32f","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"Empty version change upmerge","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/0bb654b8d9161ecf46684d040c08b86bbc74a32f"},{"sha":"ddcad361d6ff2c3336221f27c4e31bfc8d1913b1","author":{"email":"57a9461ad3972b3802cf500c927040dc082abf56@oracle.com","name":"Arun Kuruvila"},"message":"Bug #21503595 : --QUERY-ALLOC-BLOCK-SIZE=-1125899906842624 +\n                PID_FILE CHECK LEADS TO OOM SIG 11\n\nDescription:- A server started with 'query_alloc_block_size'\noption set to a certain range of negative values on a\nmachine without enough memory may lead to OOM.\n\nAnalysis:- Server uses 'strtoull()' to convert server\nvariable values of type 'GET_UINT', 'GET_ULONG' or 'GET_ULL'\nfrom string to unsigned long long. According to the man\npage, 'strtoull()' function returns either the result of the\nconversion or, if there was a leading minus sign, the\nnegation of the result of the conversion represented as an\nunsigned value, unless the original(nonnegated) value would\noverflow; in the latter case, strtoull() returns ULLONG_MAX\nand sets errno to ERANGE. So 'strtoull()' converts a small\nnegative value to a larger postive value. For example string\n'-1125899906842624' will be converted to an unsigned value,\n'18445618173802708992' (ulonglong typecast of\n'-1125899906842624'). So a\nserver started with 'query_alloc_block_size' set to\n\"-1125899906842624\" on a machine without enough memory will\nlead to OOM since server allocates '18445618173802708992'\nbytes(17178820608 GB) for query allocation block.\n\nFix:- When server is started with any server variable, of\ntype \"GET_UINT\", \"GET_ULONG\" or \"GET_ULL\", set to a negative\nvalue, a warning, \"option xxx: value -yyy adjusted to zzz\"\nis thrown and the value is adjusted to the lowest possible\nvalue for that variable. The dynamic server variable which\nis configured through the client exhibit the same behavior\nas fix made for variables configured during the server\nstart up.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/ddcad361d6ff2c3336221f27c4e31bfc8d1913b1"},{"sha":"adf12e6e1704dbf4f5e06fa45f40ab5b71514cff","author":{"email":"a9f016bc89a833193596cbc6e9f8dc2bcfb46be3@oracle.com","name":"Marko Mäkelä"},"message":"Adapt to WL#8845 Implement an InnoDB redo log format version identifier\n\nrecv_find_max_checkpoint(): Amend the error message to give advice\nabout downgrading. The 5.7.9 redo log format was intentionally changed\nso that older MySQL versions will not find a valid redo log checkpoint.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/adf12e6e1704dbf4f5e06fa45f40ab5b71514cff"},{"sha":"17387bc574a4054a9aeac7ba4aa60e25588dc7bf","author":{"email":"c94a4cc1a8d303e1d72c234073e7151292c1d979@oracle.com","name":"Shishir Jaiswal"},"message":"Bug #21467458 - UNINSTALL PLUGIN DAEMON_EXAMPLE CRASHES\n                MYSQLD.\n\nDESCRIPTION\n===========\nCrash occurs when daemon_example plugin is uninstalled\nimmediately after its installed. This can be reproduced\nby installing and uninstalling the plugin repeatedly.\n\nANALYSIS\n========\nThe daemon_example_plugin_deinit() function of the daemon\nexample plugin calls pthread_cancel() but doesn't wait for\nthe worker thread to actually complete before deallocating\nthe data buffer and closing the file that it writes to.\nThis is causing SEGFAULT!\n\nFIX\n===\nAdded a pthread_join() to wait for the thread to complete\nbefore doing the cleanup work.\n\nRemoved a stray 'x' variable from the example code.\n\nNOTE\n====\nHave made an entry in .opt file as given below:\n--plugin-dir=$DAEMONEXAMPLE_DIR\n\nThis is done so that the program takes plugin directory as\n../<dbg>/plugin/daemon_example/ instead of\n../lib/plugin/","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/17387bc574a4054a9aeac7ba4aa60e25588dc7bf"},{"sha":"4acc7615eedc167fbad6fcc14966a054de35fd75","author":{"email":"675b1c4b9de061e0ce011ae43a19257c7860586d@oracle.com","name":"Sreeharsha Ramanavarapu"},"message":"Bug #19929406: HANDLE_FATAL_SIGNAL (SIG=11) IN\n               __MEMMOVE_SSSE3_BACK FROM STRING::COPY\n\nIssue:\n-----\nWhile using row comparators, the store_value functions call\nval_xxx functions in the prepare phase. This can cause\nvalgrind issues.\n\nSOLUTION:\n---------\nSetting up of the comparators should be done by\nalloc_comparators in the prepare phase. Also, make sure\nstore_value will be called only during execute phase.\n\nThis is a backport of the fix for Bug#17755540.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/4acc7615eedc167fbad6fcc14966a054de35fd75"},{"sha":"0632dae73fe3379cba00beeb65585f0d61f10d8c","author":{"email":"e1ee07a635325969c40a25dfd4daafeabf40d088@oracle.com","name":"Robert Golebiowski"},"message":"Bug #21025377 CAN'T CONNECT TO SSL ENABLED SERVER FIRST 30 SEC AFTER\nINITIAL STARTUP\n\nUpdated yassl to yassl-2.3.7e","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/0632dae73fe3379cba00beeb65585f0d61f10d8c"},{"sha":"259cf3dc607dd0112d44c4647b07a3024cee268e","author":{"email":"e1ee07a635325969c40a25dfd4daafeabf40d088@oracle.com","name":"Robert Golebiowski"},"message":"Updated yassl to yassl-2.3.8","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/259cf3dc607dd0112d44c4647b07a3024cee268e"},{"sha":"8ea80ecfeb88846ee47c65011eb9ff7eddab84b3","author":{"email":"3dd7fa59519d1d3dbf7043cc4f1397eca520ea4c@oracle.com","name":"Annamalai Gurusami"},"message":"Bug #19929435 DROP DATABASE HANGS WITH MALFORMED TABLE\n\nNote: Backporting the patch from mysql-5.6.\n\nProblem:\n\nA CREATE TABLE with an invalid table name is detected\nat SQL layer. So the table name is reset to an empty\nstring.  But the storage engine is called with this\nempty table name.  The table name is specified as\n\"database/table\".  So, in the given scenario we get\nonly \"database/\".\n\nSolution:\n\nWithin InnoDB, detect this error and report it to\nhigher layer.\n\nrb#9274 approved by jimmy.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/8ea80ecfeb88846ee47c65011eb9ff7eddab84b3"},{"sha":"86375f7fa6a428bfc405f85335685cd1dff25302","author":{"email":"57a9461ad3972b3802cf500c927040dc082abf56@oracle.com","name":"Arun Kuruvila"},"message":"Bug #21370329 : FLUSH DES_KEY_FILE MAY NOT WORK\n\nDescription: The command FLUSH DES_KEY_FILE is expected to\nreload the DES keys from the file that was specified with\nthe \"--des-key-file\" option at server startup. But it is not\nbehaving as expected.\n\nAnalysis: The des file reload is defined within a wrong\nconditional directive, rendering the command ineffective.\nMacro \"OPENSSL\" was used instead of \"HAVE_OPENSSL\" macro.\n\nFix: \"OPENSSL\" macro is changed to \"HAVE_OPENSSL\".","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/86375f7fa6a428bfc405f85335685cd1dff25302"},{"sha":"ea9dbef661efdf5079b1b0e33679a863408e3166","author":{"email":"2602d191743ee4fe25728cd2d76dfdc26d11c751@oracle.com","name":"Aditya A"},"message":"Bug#20755615    CREATING INDEX ON A RENAMED COLUMN WITH CASE CRASH .FRM\n                FILE\n\nPROBLEM\n\nIn 5.5 when doing doing a rename of a column ,we ignore the case between\nold and new column names while comparing them,so if the change is just\nthe case then we don't even mark the field FIELD_IS_RENAMED ,we just update\nthe frm file ,but don't recreate the table as is the norm when alter is\nused.This leads to inconsistency in the innodb data dictionary which causes\nindex creation to fail.\n\nFIX\n\nAccording to the documentation any innodb column rename should trigger\nrebuild of the table. Therefore for innodb tables we will do a strcmp()\nbetween the column names and if there is case change in column name\nwe will trigger a rebuild.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/ea9dbef661efdf5079b1b0e33679a863408e3166"},{"sha":"8ea58c474fbbcd79e9716379d226b8a46062b350","author":{"email":"4025aab300f58d3c3c34aa0a55f93939eedaf2b8@oracle.com","name":"Balasubramanian Kandasamy"},"message":"    BUG 21900800 - ADD OBSOLETE ON MYSQL-CONNECTOR-C-SHARED AND MYSQL-CONNECTOR-C-DEVEL\n\n    As MySQL Connector C 6.1 is end of life, added conflict with mysql-connector-c-shared dependencies","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/8ea58c474fbbcd79e9716379d226b8a46062b350"},{"sha":"f83d9e4217827b4d0b078bc93dff7d8f173adbef","author":{"email":"86299e0df4224214cf4406b6c97f7213e45bc2f6@oracle.com","name":"Gipson Pulla"},"message":"Merge branch 'mysql-5.5.46-release' into mysql-5.5","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/f83d9e4217827b4d0b078bc93dff7d8f173adbef"},{"sha":"415faa122b9c683661dafac82fff414fa6864151","author":{"email":"675b1c4b9de061e0ce011ae43a19257c7860586d@oracle.com","name":"Sreeharsha Ramanavarapu"},"message":"Bug #19434916: FATAL_SIGNAL IN ADD_KEY_EQUAL_FIELDS() WITH\n               UPDATE VIEW USING OUTER SUBQUERY\n\nIssue:\n-----\nWhile resolving a column which refers to a table/view in an\nouter query, it's respecitve item object is marked with the\nouter query's select_lex object. But when the column refers\nto a view or if the column is part of a subquery in the\nHAVING clause, an Item_ref object is created. While the\nreference to the outer query is stored by the Item_ref\nobject, the same is not stored in it's real_item.\n\nThis creates a problem with the IN-TO-EXISTS optmization.\nWhen there is an index over the column in the inner query,\nit will be considered since the column's real_item object\nwill be mistaken for a local field. This will lead to a\ncrash.\n\nSOLUTION:\n---------\nUnder the current design, the only way to fix this issue is\nto check the reginfo.join_tab for a NULL value. If yes, the\nquery should not be worrying about the key use.\n\nThe testcase and comments added as part of the fix for\nBug#17766653 have been backported.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/415faa122b9c683661dafac82fff414fa6864151"},{"sha":"130b5fbf91520e504194eb59c16a6ce38006ff7a","author":{"email":"675b1c4b9de061e0ce011ae43a19257c7860586d@oracle.com","name":"Sreeharsha Ramanavarapu"},"message":"Bug #19894161: FATAL SIGNAL 11 IN\n               CONVERT_CHARSET_PARTITION_CONSTANT:\n               SQL/SQL_PARTITION..CC:202\n\nIssue:\n-----\nThis problem happens under the following conditions:\n1) A table partitioned with a character column as the key.\n2) The expressions specified in the partition definition\n   requires a charset conversion. This can happen when the\n   server's default collation is different from the\n   expression's collation.\n3) INSERT DELAYED is used to insert data into the table.\n\nSOLUTION:\n---------\nWhile creating the delayed_insert object, initialize it\nwith the relevant select_lex.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/130b5fbf91520e504194eb59c16a6ce38006ff7a"},{"sha":"ecfc7c26166687d4ffb0ae13f518f44f256b9d65","author":{"email":"da39a3ee5e6b4b0d3255bfef95601890afd80709","name":"mysql-builder@oracle.com"},"message":"","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/ecfc7c26166687d4ffb0ae13f518f44f256b9d65"},{"sha":"f92dd6ae6fb8922122049957b6ab7e07b6518bc2","author":{"email":"57687871af7f47895a7e21d9802a5e3cfba15870@oracle.com","name":"Mithun C Y"},"message":"Bug #20007383: HANDLE_FATAL_SIGNAL (SIG=11) IN UPDATE_REF_AND_KEYS.\n\nIssue:\n======\nThe fulltext predicate is inside a subquery and involves\nan outer reference; it thus cannot be used for FT index look-up,\nbut MySQL does not see it, which causes a illegal access.\n\nSolution:\n=========\nSolution is backported from bug#21140088. Outer reference can\nnot be used as argument of the MATCH function. Added check for\nouter reference.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/f92dd6ae6fb8922122049957b6ab7e07b6518bc2"},{"sha":"3846b085521bce8e4600d4860dc3f2ea5f2ceb2d","author":{"email":"57a9461ad3972b3802cf500c927040dc082abf56@oracle.com","name":"Arun Kuruvila"},"message":"Bug #21602056 : CONCURRENT FLUSH PRIVILEGES + REVOKE/GRANT\n                CRASHES IN WILD_CASE_COMPARE!\n\nDescription:- Executing FLUSH PRIVILEGES and REVOKE/\nGRANT concurrently crashes the server.\n\nAnalysis:- Concurrent FLUSH PRIVILEGES and REVOKE/GRANT\nmight trigger a small time frame in which REVOKE/GRANT\nfetches the \"acl_proxy_user\" information as a part of\n\"acl_check_proxy_grant_access()\". Meanwhile FLUSH PRIVILEGES\ndeletes the old acl structures as a part of \"acl_reload()\".\nAfter which REVOKE/GRANT tries to access the hostname in\n\"wild_case_compare()\" which leads to a crash because of the\ninvalid memory access.\n\nFix:- Mutex lock on \"acl_cache\" is acquired before fetching\n\"acl_proxy_user\" information in\n\"acl_check_proxy_grant_access()\".","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/3846b085521bce8e4600d4860dc3f2ea5f2ceb2d"},{"sha":"a86191c69c95240ba3dcd9858341a30898c34285","author":{"email":"57a9461ad3972b3802cf500c927040dc082abf56@oracle.com","name":"Arun Kuruvila"},"message":"Bug #21235226 : THE --ENABLE-CLEARTEXT-PLUGIN IS NOT\n                IMPLEMENTED IN ALL CLIENT PROGRAMS\n\nDescription: Option \"enable-cleartext-plugin\" is not\navailable for the following client utilities:-\nmysqldump\nmysqlimport\nmysqlshow\nmysqlcheck\n\nAnalysis: The unavailability of this option limits the\nfeatures like PAM authentication from using the above\nmentioned utilities.\n\nFix: Option \"enable-cleartext-plugin\" is implemented in the\nabove mentioned client utilities.","distinct":false,"url":"https://api.github.com/repos/MariaDB/server/commits/a86191c69c95240ba3dcd9858341a30898c34285"}]}