Path to this page:
Subject: CVS commit: pkgsrc/databases
From: John Nemeth
Date: 2020-10-25 23:38:58
Message id: 20201025223858.D433AFB28@cvs.NetBSD.org
Log Message:
Update MySQL 5.6 to 5.6.50.
Note that the 5.6 series will be end of life in February 2021. The
current major version is 8.0, which isn't in pkgsrc yet. You CAN NOT
upgrade directly from 5.6 to 8.0, therefore it is recommended for anybody
running 5.6 to upgrade to this version, then upgrade to 5.7.
Changes in MySQL 5.6.50 (2020-10-19, General Availability)
Functionality Added or Changed
LOCK TABLES privilege checking for views was improved. (Bug #31304432)
Bugs Fixed
InnoDB: In session started with START TRANSACTION WITH CONSISTENT
SNAPSHOT, a range query returned a truncated result. The end
range flag was not reset at the beginning of the index read
resulting in an aborted read and missing rows. (Bug #30950714,
Bug #98642)
References: This issue is a regression of: Bug #23481444.
In bootstrapping mode, certain multiple-statement transactions
could cause unexpected server behavior. (Bug #31650096)
Assigning CONCAT('') or CONCAT_WS('') to a variable set the
variable to NULL, not the empty string. (Bug #31320716, Bug
#99485, Bug #31413167, Bug #99722)
ORDER BY queries were not executed correctly when sort_buffer_size
and max_sort_length were set to values which caused the internal
limit on the maximum number of keys allowed per sort buffer to
be set to 0. (Bug #30175483)
The internal method Field_tiny::pack() did not always perform
bounds checking as expected. (Bug #29948029)
References: See also: Bug #31591391.
A large number of nested arguments in full-text search query
caused an error. (Bug #29929684)
An assertion could be raised when the SQL layer passed incorrect
information to InnoDB about the type of operation to be performed
on a temporary table. (Bug #22503696)
Files: