{"push_id":1335078163,"size":13,"distinct_size":13,"ref":"refs/heads/joyent/feature/backports/2014Q4","head":"171742ca5f9c3e1f508d65e6295d5c622d199a70","before":"560e4b769fa65668206aebd0d0fd67ffad49dab6","commits":[{"sha":"266c347be28e05c403eb1b7b44a40528561333c1","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.5.48:\n* yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites.\n* The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11.\n* Bugs Fixed","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/266c347be28e05c403eb1b7b44a40528561333c1"},{"sha":"955c5f39bc9c54f6b9e29e02847924f5e146cdcf","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.6.29:\n* InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement.\n* yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites.\n* The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11.\n* Bugs Fixed","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/955c5f39bc9c54f6b9e29e02847924f5e146cdcf"},{"sha":"ef112ad371008a39fd23cb758ba2af88a98aca35","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.5.49:\n\nSecurity Notes\n--------------\nMySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. The default value is DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be specified to require a secure connection, or fail if a secure connection cannot be obtained.\n\nThese clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade.\n\nFor more information, see Command Options for Secure Connections.\n\nBugs Fixed","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/ef112ad371008a39fd23cb758ba2af88a98aca35"},{"sha":"43bba0013d94b342e90fbca285ef7501e6009080","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.6.30:\n\nSecurity Notes\n--------------\nThe linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1s. Issues fixed in the new version are described at http://www.openssl.org/news/vulnerabilities.html.\n\nThis change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead.\n\nMySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. The default value is DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be specified to require a secure connection, or fail if a secure connection cannot be obtained.\n\nThese clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade.\n\nFor more information, see Command Options for Secure Connections.\n\nBugs Fixed","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/43bba0013d94b342e90fbca285ef7501e6009080"},{"sha":"883e9f0d2142139a5704cd542ca810f156c5d910","author":{"name":"fhajny","email":"0d61f72ee450e409989c5dfce1c9d83f41625b62"},"message":"Use proper CONF_FILES for my.cnf. Makes mysql56-client look for it\nunder $PKG_SYSCONFDIR, and prevents mysql_install_db from creating\n$PREFIX/my.cnf. Brings mysql56-client and mysql56-server in sync\nWRT my.cnf location. Bump respective PKGREVISIONs.\n\nNoticed by peterkelm@ on Github.","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/883e9f0d2142139a5704cd542ca810f156c5d910"},{"sha":"189122142f45e8632ef9dacaee0fbe317e5a7de5","author":{"name":"fhajny","email":"0d61f72ee450e409989c5dfce1c9d83f41625b62"},"message":"Remove stray chunk from patch file. Ride previous revision.","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/189122142f45e8632ef9dacaee0fbe317e5a7de5"},{"sha":"8117f8edd19565089493d0dbaa19d2e284c0e17f","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.5.0:\n\nFunctionality Added or Changed\n\nThe version of the tcmalloc library included in MySQL distributions was very old. It has been removed and is no longer included with MySQL.\n\n\nBugs Fixed\n\nINSERT with ON DUPLICATE KEY UPDATE and REPLACE on a table with a foreign key constraint defined failed with an incorrect “duplicate entry” error rather than a foreign key constraint violation error.\n\nSetting sort_buffer_size to a very large value could cause some operations to fail with an out-of-memory error.\n\nSeveral potential buffer overflow issues were corrected.\n\nIf the CA certificate as given to the --ssl-ca option had an invalid path, yaSSL returned an error message different from OpenSSL. Now both return SSL connection error: SSL_CTX_set_default_verify_paths failed.\n\nSome string functions returned one or a combination of their parameters as their result. If one of the parameters had a non-ASCII character set, the result string had the same character set, resulting in incorrect behavior when an ASCII string was expected.\n\nA null pointer dereference of a parser structure could occur during stored procedure name validation.\n\nmysqld_multi displayed misleading error messages when it was unable to execute my_print_defaults.","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/8117f8edd19565089493d0dbaa19d2e284c0e17f"},{"sha":"7b04a17c4304a606d426c4f573a64e6c71adaa77","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.6.31:\n\nSecurity Notes\n\nThe linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1t. Issues fixed in the new version are described at http://www.openssl.org/news/vulnerabilities.html.\n\nThis change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug 23229564)\n\nFunctionality Added or Changed\n\nA new CMake option, WITH_SYMVER16, if enabled, causes the libmysqlclient client library to contain extra symbols to be compatible with libmysqlclient on RHEL/OEL 5, 6, 7, and Fedora releases. All symbols present in libmysqlclient.so.16 are tagged with symver 16 in libmsqlclient.so.18, making those symbols have both symver 16 and 18. (Bug 22980983)\n\nsupport-files/MacOSX/ReadMe.txt is no longer included in MySQL distributions. (Bug 81038, Bug 23088916)\n\nThe version of the tcmalloc library included in MySQL distributions was very old. It has been removed and is no longer included with MySQL. (Bug 80994, Bug 23068660)\n\nBugs Fixed\n\nInnoDB: MySQL failed to build on Fedora 24 using GCC 6. (Bug 23227804)\n\nInnoDB: Potential buffer overflow issues were corrected for the InnoDB memcached plugin. (Bug 23187607)\n\nInnoDB: The full-text index cache was freed during a background index cache synchronization. (Bug 22996488)\n\nInnoDB: A full-text index operation raised an assertion. (Bug 22963169)\n\nInnoDB: An INSERT operation on a table with a FULLTEXT index and FTS_DOC_ID column failed because the inserted FTS_DOC_ID value exceeded the permitted gap between consecutive FTS_DOC_ID values. To avoid this problem, the permitted gap between the largest used FTS_DOC_ID value and new FTS_DOC_ID value was raised from 10000 to 65535. (Bug 22679185)\n\nInnoDB: With innodb_autoinc_lock_mode=0, multiple threads waiting for a table-level lock caused an unexpected deadlock. (Bug 21983865, Bug 78761)\n\nInnoDB: A FLUSH TABLES ... FOR EXPORT operation appeared to stall. A loop in the ibuf_contract_in_background function failed to exit. (Bug 21133329, Bug 77011)\n\nInnoDB: A full-text query raised an assertion. Under certain circumstances, DDL operations such as ALTER TABLE ... RENAME caused full-text auxiliary tables to be removed on server restart. (Bug 13651665)\n\nReplication: In the next_event() function, which is called by a slave's SQL thread to read the next even from the relay log, the SQL thread did not release the relaylog.log_lock it acquired when it ran into an error (for example, due to a closed relay log), causing all other threads waiting to acquire a lock on the relay log to hang. With this fix, the lock is released before the SQL thread leaves the function under the situation. (Bug 21697821)\n\nReferences: See also: Bug 20492319.\n\nReplication: If a multi-threaded replication slave running with relay_log_recovery=1 stopped unexpectedly, during restart the relay log recovery process could fail. This was due to transaction inconsistencies not being filled, see Handling an Unexpected Halt of a Replication Slave. Prior to this fix, to recover from this situation required manually setting relay_log_recovery=0, starting the slave with START SLAVE UNTIL SQL_AFTER_MTS_GAPS to fix any transaction inconsistencies and then restarting the slave with relay_log_recovery=1. This process has now been automated, enabling relay log recovery of a multi-threaded slave upon restart automatically. (Bug 77496, Bug 21507981)\n\nINSERT with ON DUPLICATE KEY UPDATE and REPLACE on a table with a foreign key constraint defined failed with an incorrect “duplicate entry” error rather than a foreign key constraint violation error. (Bug 23135731)\n\nReferences: This issue is a regression of: Bug 78853, Bug 22037930.\n\nFor debug builds, CONCAT_WS() could raise an assertion if there was nothing to append. (Bug 22888420)\n\nInvoking Enterprise Encryption functions in multiple threads simultaneously could cause a server exit. (Bug 22839278)\n\nAttempting to use Enterprise Encryption functions after creating and dropping them could cause a server exit. (Bug 22669012)\n\nSetting sort_buffer_size to a very large value could cause some operations to fail with an out-of-memory error. (Bug 22594514)\n\nAn assertion could be raised when a deadlock occurred due to a SELECT ... GROUP BY ... FOR UPDATE query executed using a Loose Index Scan. (Bug 22187476)\n\nSeveral potential buffer overflow issues were corrected. (Bug 21977380, Bug 23187436, Bug 23202778, Bug 23195370, Bug 23202699)\n\nIf the CA certificate as given to the --ssl-ca option had an invalid path, yaSSL returned an error message different from OpenSSL. Now both return SSL connection error: SSL_CTX_set_default_verify_paths failed. (Bug 21920657)\n\nSome string functions returned one or a combination of their parameters as their result. If one of the parameters had a non-ASCII character set, the result string had the same character set, resulting in incorrect behavior when an ASCII string was expected. (Bug 18740222)\n\nOn Windows, MySQL installation could result in MySQL being placed under C:\\Program Files\\Canon\\Easy-WebPrint EX. (Bug 14583183)\n\nReferences: See also: Bug 70918, Bug 68821, Bug 68227.\n\nOn Fedora 24, upgrades using a Community MySQL Server RPM failed to replace an installed MariaDB Galera server due to a change in the MariaDB package. (Bug 81390, Bug 23273818)\n\nMySQL did not compile under Solaris 12 using Sun Studio. To correct this, instances of __attribute__ were changed to MY_ATTRIBUTE. (Bug 80748, Bug 22932576)\n\nThe INSTALL-SOURCE file had partly outdated information and has been removed from source packages. (Binary packages are unaffected). (Bug 80680, Bug 23081064)\n\nFor a server compiled with -DWITH_PERFSCHEMA_STORAGE_ENGINE=0, a memory leak could occur for buffered log messages used during server startup. (Bug 80089, Bug 22578574)\n\nFor debug builds, merging a derived table into an outer query block could raise an assertion. (Bug 79502, Bug 22305361, Bug 21139722)\n\nA null pointer dereference of a parser structure could occur during stored procedure name validation. (Bug 79396, Bug 22286421)\n\nUsing CREATE USER to create an account with the mysql_native_password or mysql_old_password authentication plugin and using a clause of the form IDENTIFIED WITH plugin AS 'hash_string' caused the account to be created without a password. (Bug 78033, Bug 21616496)\n\nFailure of UNINSTALL PLUGIN could lead to inaccurate or confusing errors for subsequent INSTALL PLUGIN operations. (Bug 74977, Bug 20085672)\n\nmysqld_multi displayed misleading error messages when it was unable to execute my_print_defaults. (Bug 74636, Bug 19920049)\n\nOn Windows, MySQL installation failed if the HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\ registry key was present with a key/value pair of \"InstallLocation\" and \"\\Hewlett-Packard\\\\\". (Bug 74631, Bug 19949163)\n\nmysqldump failed silently with no error message when it encountered an error while executing FLUSH LOGS.","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/7b04a17c4304a606d426c4f573a64e6c71adaa77"},{"sha":"fbf3af9001c4cc5f0b8fa76a19a12ab2d2342c1b","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.6.32:\nBugs Fixed\n\nInnoDB: Full-text search auxiliary tables could be dropped by one session while being access by another.\n\nInnoDB: Selecting full-text index information schema tables for a deleted table caused a segmentation fault.\n\nInnoDB: Rollback of a full-text index synchronization operation raised an assertion. The rollback operation attempted to acquire a mutex still held by the background synchronization thread.\n\nInnoDB: Setting innodb_monitor_enable to all did not enable all counters.\n\nReplication: After issuing a PURGE BINARY LOGS statement, if the binary log index file was not available, for example because it had been opened by another application such as MEB, the server could stop unexpectedly. Although this situation was rare, the handling has been made more robust to avoid unexpected halts and more informative errors are provided.\n\nReplication: When using row-based replication and InnoDB, replication slaves reverted to using an older locking scheme when a transaction had already acquired an AUTOINC lock related to a LOAD FILE or INSERT ... SELECT type of statement, reducing replication slave performance. The fix ensures that sql_command is set correctly for any of the DML events such as WRITE_ROWS_EVENT, UPDATE_EVENT, and DELETE_EVENT.\n\nReplication: A MySQL version 5.5 slave does not have a server_uuid and replication identified servers by their server_id. Starting from MySQL version 5.6, replication masters detected a zombie dump thread based only on a slave's server_uuid value, under the assumption that each slave has a unique UUID. Connecting a MySQL 5.5 slave to a MySQL 5.6 and later master meant that the master was unable to detect zombie dump threads that were created to serve slaves running versions older than MySQL 5.6. The fix ensures that a master now first checks if a slave has a server_uuid set. If it is set, zombie dump thread detection happens based on the slave's UUID. If a slave's server_uuid is not set, zombie dump thread detection happens based on server_id.\n\nReplication: With slave_skip_errors enabled there were still special cases when slave errors were not being correctly ignored. For example:\n\nWhen opening and locking a table failed.\n\nWhen field conversions failed on a server running row-based replication.\n\nIn these cases the error was considered critical and it was not respecting the state of slave_skip_errors. The fix ensures that with slave_skip_errors enabled, all errors reported during applying a transaction are correctly handled. This means that in such a set up, upon receiving an error with the log_warnings option set to greater than 1, if the error can be ignored then the warning is printed into the error log and the server continues as it does in the case of other ignored errors.\n\nReplication: When using statement-based or mixed binary logging format with --read-only=ON, it was not possible to modify temporary tables.\n\nMySQL Server upgrades performed using RPM packages failed when upgrading from MySQL 5.5 Community to MySQL 5.6 Community or MySQL 5.5 Commercial to MySQL 5.6 Commercial.\n\nThe code for reading character set information from Performance Schema statement events tables (for example, events_statements_current) did not prevent simultaneous writing to that information. As a result, the SQL query text character set could be invalid, which could result in a server exit. Now an invalid character set causes SQL_TEXT column truncation.\n\nA buffer overflow in the regex library was fixed.\n\nCertain arguments to NAME_CONST() could cause a server exit.\n\nFor unit-testing with the MySQL test suite, the make unit-test command is no longer available. The ctest program should be used instead. See Unit Tests Added to Main Test Runs.\n\nST_Distance() could raise an assertion for NULL return values.\n\nWith the query cache enabled, executing a prepared statement with CURSOR_TYPE_READ_ONLY and then again with CURSOR_TYPE_NO_CURSOR caused the server to return an error.\n\nmysql_real_connect() was not thread-safe when invoked with the MYSQL_READ_DEFAULT_FILE or MYSQL_READ_DEFAULT_GROUP option enabled.\n\nInstalling MySQL from a yum or zypper repository resulted in /var/log/mysqld.log being created with incorrect user and group permissions.\n\nIf a stored function updated a view for which the view table had a trigger defined that updated another table, it could fail and report an error that an existing table did not exist.\n\nIf an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared library name, it caused the server to hang (or to raise an assertion in debug builds).\n\nFor multibyte character sets, LOAD DATA could fail to allocate space correctly and ignore input rows as a result.","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/fbf3af9001c4cc5f0b8fa76a19a12ab2d2342c1b"},{"sha":"b4d98a651c6ae96c7117b5732a66087d030d8851","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes 5.5.51:\nBugs Fixed\n\nReplication: When using statement-based or mixed binary logging format with --read-only=ON, it was not possible to modify temporary tables.\n\nMySQL Server upgrades performed using RPM packages failed when upgrading from MySQL 5.1 Community to MySQL 5.5 Community or MySQL 5.1 Commercial to MySQL 5.5 Commercial.\n\nA buffer overflow in the regex library was fixed.\n\nCertain arguments to NAME_CONST() could cause a server exit.\n\nInstalling MySQL from a yum or zypper repository resulted in /var/log/mysqld.log being created with incorrect user and group permissions.\n\nIf a stored function updated a view for which the view table had a trigger defined that updated another table, it could fail and report an error that an existing table did not exist.\n\nIf an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared library name, it caused the server to hang (or to raise an assertion in debug builds).\n\nFor multibyte character sets, LOAD DATA could fail to allocate space correctly and ignore input rows as a result.","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/b4d98a651c6ae96c7117b5732a66087d030d8851"},{"sha":"073b4f6eddf18026e04d02b40ebecca1815f86e3","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes in MySQL 5.6.33 (2016-09-06)\n\nTest Suite Notes\n----------------\nIn mysql-test-run.pl, a limit of 50 was imposed on the number of workers for parallel testing, which on systems with more than 50 CPUs resulted in exhaustion of unique thread IDs. The ID-exhaustion problem has been corrected, and the limit of 50 on number of workers has been lifted. Thanks to Daniel Black for the patch on which this change was based. Additionally, these changes were made:\n\nTo avoid idle workers, the number of parallel workers now is limited to the number of tests.\n\nPreviously, if --parallel=auto was given and the MTR_MAX_PARALLEL environment variable was not set, a limit of 8 was imposed on the number of parallel workers. This limit has been lifted.\n\n(Bug 22342399, Bug 79585)\n\nFunctionality Added or Changed\n------------------------------\nCMake support for compiling with Solaris Studio 12.5 was added. (Bug 82249, Bug 24303829, Bug 81274, Bug 23212938)\n\nBugs Fixed\n----------\nInnoDB: An operation that dropped and created a full-text search table raised an assertion. (Bug 24315031)\n\nInnoDB: Accessing full-text search auxiliary tables while dropping the indexed table raised an assertion. (Bug 24009272)\n\nInnoDB: An online DDL operation on a table with indexed BLOB columns raised an assertion during logging of table modifications. (Bug 23760086)\n\nReplication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new connection for log2 without freeing the connection used for log1. Thanks to Laurynas Biveinis for the contribution. (Bug 81675, Bug 23540182)\n\nReplication: With binlog_row_image=FULL, when updating single tables temporary tables were unnecessarily being used. The fix ensures single table update follows the same pattern as multi-table update. (Bug 79867, Bug 22510353)\n\nFor mysqld_safe, the argument to --malloc-lib now must be one of the directories /usr/lib, /usr/lib64, /usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In addition, the --mysqld and --mysqld-version options can be used only on the command line and not in an option file. (Bug 24464380)\n\nIt was possible to write log files ending with .ini or .cnf that later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with .ini or .cnf. (Bug 24388753)\n\nPrivilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug 24388746)\n\nIf the basedir system variable was set at server startup from the command line or option file, the value was not normalized (on Windows, / was not replaced with /). (Bug 23747899, Bug 82125)\n\nIn-place ALTER TABLE operations which when executed separately caused no table rebuild could when combined into a single statement result in a table rebuild. (Bug 23475211, Bug 81587)\n\nA blank server name in CREATE SERVER statements produced a server exit rather than an error. (Bug 23295288)\n\nA prepared statement that used a parameter in the select list of a derived table that was part of a join could cause a server exit. (Bug 22392374, Bug 24380263)\n\nMEDIUMINT columns used in operations with long integer values could result in buffer overflow. (Bug 19984392)\n\nA spurious ER_NO_SUCH_TABLE error could occur when attempting to execute a prepared CREATE TABLE ... SELECT statement that used a temporary table in the FROM clause and called a stored function. The same error could occur for a nonprepared version of the statement if used in a stored procedure when the procedure was re-executed. (Bug 16672723, Bug 68972)\n\nEINTR handling in the client library has been fixed so that interrupted read and write calls are retried. Previously, EINTR was ignored. (Bug 82019, Bug 23703570)","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/073b4f6eddf18026e04d02b40ebecca1815f86e3"},{"sha":"ef5d35a2b6a49f119ad1eac5705ba387a2b711d7","author":{"name":"adam","email":"50deb78d4601f4b197cde493023ef6c76db172af"},"message":"Changes in MySQL 5.5.52 (2016-09-06)\n\nBugs Fixed\n----------\nReplication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new connection for log2 without freeing the connection used for log1. Thanks to Laurynas Biveinis for the contribution. (Bug 81675, Bug 23540182)\n\nFor mysqld_safe, the argument to --malloc-lib now must be one of the directories /usr/lib, /usr/lib64, /usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In addition, the --mysqld and --mysqld-version options can be used only on the command line and not in an option file. (Bug 24464380)\n\nIt was possible to write log files ending with .ini or .cnf that later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with .ini or .cnf. (Bug 24388753)\n\nPrivilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug 24388746)\n\nCertain internal character-handling functions could fail to handle a too-large character and cause a server exit. (Bug 23296299)\n\nA blank server name in CREATE SERVER statements produced a server exit rather than an error. (Bug 23295288)\n\nThe optimizer failed to check a function return value for an area calculation, leading to a server exit. (Bug 23280059)\n\nA prepared statement that used a parameter in the select list of a derived table that was part of a join could cause a server exit. (Bug 22392374, Bug 24380263)\n\nMEDIUMINT columns used in operations with long integer values could result in buffer overflow. (Bug 19984392)\n\nEINTR handling in the client library has been fixed so that interrupted read and write calls are retried. Previously, EINTR was ignored. (Bug 82019, Bug 23703570)","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/ef5d35a2b6a49f119ad1eac5705ba387a2b711d7"},{"sha":"171742ca5f9c3e1f508d65e6295d5c622d199a70","author":{"name":"abs","email":"52fad529929444ac58c7122f855cdfa32c3bd2bf"},"message":"Add missing entry to REPLACE_PERL","distinct":true,"url":"https://api.github.com/repos/joyent/pkgsrc/commits/171742ca5f9c3e1f508d65e6295d5c622d199a70"}]}
{"actor":{"display_login":"mamash"}}