non port: databases/mysql80-server/files/patch-client_CMakeLists.txt |
Number of commits found: 14 |
Wednesday, 19 Mar 2025
|
09:58 Jochen Neumeister (joneum) Author: Christos Chatzaras
databases/mysql80-{client, server}: Update to 8,0.41
Bugs Fixed
Incompatible Change: Corruption occurred in a spatial index when an
update of a geometry with a minimal change in the minimum bounding
rectangle (MBR) was followed by a delete operation.
When upgrading to this release, it is recommended that you drop any
spatial indexes beforehand, then re-create them after the upgrade is
complete. Alternatively, you can drop and re-create such indexes
immediately following the upgrade, but before making use of any of the
tables in which they occur. You should also be aware that downgrading to
any previous version reintroduces the original problem described
previously.
For more information, see Creating Spatial Indexes. (Bug #36452528)
InnoDB: Concurrently truncating a table while querying the
Performance Schema sometimes cause MySQL to halt unexpectedly. (Bug
InnoDB: It was possible for an ALTER TABLE operation using the
INPLACE algorithm on a table containing both a spatial index and an
auto-increment column to cause corruption or, in debug builds, to
trigger a debug assert. This was due to the auto-increment column value
being overwritten in the old records of the spatial index while the new
record was prepared. (Bug #37189985)
InnoDB: Certain IO buffer serializations triggered an assertion in
debug builds that caused the system to hang. (Bug #37139618)
InnoDB: Improved InnoDB start up time. (Bug #36880863)
References: This issue is a regression of: Bug #36808732.
InnoDB: An assertion failure was raised when creating a FULLTEXT
index on a table with an FTS_DOC_ID value greater than 4294967295. (Bug
References: See also: Bug #37387224.
InnoDB: Dropping a primary key, and then adding a new AUTO_INCREMENT
column as a primary key in descending order using the INPLACE algorithm
failed.
Our thanks to Shaohua Wang and the team at Alibaba for the
contribution. (Bug #36658450)
InnoDB: Extending a user tablespace produces file extension redo log
records (MLOG_FILE_EXTEND), but they were not produced when extending
the system tablespace. (Bug #36511673)
InnoDB: A DELETE operation on a table with a self referential
foreign key and full-text index could have triggered an assertion. (Bug
InnoDB: When clearing an AHI index from all buffer pool pages, the
block state would potentially change to BUF_BLOCK_MEMORY before
acquiring the block mutex thus causing an unexpected halt. (Bug
InnoDB: Common prefix compression for redo log inserts
(MLOG_REC_INSERT) was disabled but is now enabled when the versions
match. (Bug #34946626)
References: This issue is a regression of: Bug #13899.
InnoDB: Virtual column information for a row containing an
externally stored BLOB was not always logged during an UPDATE operation,
which sometimes resulted in an Index PRIMARY is corrupted error. (Bug
InnoDB: ON DELETE CASCADE with generated columns containing
secondary indexes sometimes failed, due to virtual column templates not
being initialized before deletion.
Full Changelog see:
- https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-41.html
- https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-40.html
PR: 285112
Sponsored by: Netzkommund GmbH
92fc4ba |
Wednesday, 31 Jul 2024
|
08:07 Oleksii Samorukov (samm)
databases/mysql80-server: Update to 8.0.39
- fixes multiple CVEs
- fixed startup error with large table set
PR: 280455
25218e3 |
Tuesday, 22 Feb 2022
|
19:36 Dima Panov (fluffy)
databases/mysql80-server: bring back mysql_secure_installation (+)
Typo in patchfile leads to skip mysql_secure_installation.
Bring it back.
PR: 262123
Submitted by: amdmi3
Approved by: joneum (implicit)
c4ac829 |
Thursday, 10 Feb 2022
|
22:13 Jochen Neumeister (joneum)
databases/mysql80-server: Fix typo
Sponsored by: Netzkommune GmbH
8f38dec |
Thursday, 25 Nov 2021
|
07:17 Jochen Neumeister (joneum)
databases/mysql80-*: Update to 8.0.27
Release Notes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-27.html
Sponsored by: Netzkommune GmbH
ea739e8 |
Thursday, 20 May 2021
|
12:07 Dima Panov (fluffy)
databases/mysql80-*: update to 8.0.25 GA release
Release notes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-25.html
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html
PR: 255937
Submitted by: delphij@
Approved by joneum@ (implicit)
MFH: 2021Q2
c7fbbf1 |
Wednesday, 3 Feb 2021
|
14:12 fluffy
databases/mysql80-server: regen patch-client_CMakeLists.txt
PR: 253198
 |
Wednesday, 8 Jan 2020
|
16:47 joneum
databases/mysql80-{client, server}: Update to latest release 8.0.18
switch patch-files to mysql80-server to make it easy for maintain.
Bugfix:
- CMake now enables use of fastcov if it is available. fastcov is faster than
lcov or gcov. This requires GCC and gcov versions of 9 or higher.
- The DISABLE_SHARED CMake option was unused and has been removed.
- The CMake code to find Protobuf executables now works on platforms that split
these into multiple packages.
- The new ADD_GDB_INDEX CMake option determines whether to enable generation of
a .gdb_index section in binaries, which makes loading them in a debugger faster.
The option is disabled by default. It has no effect if a linker other than lld
or GNU gold is used.
- For the INSTALL_LAYOUT CMake option, the SLES and WIN option values were not
used and have been removed.
- The max_prepared_stmt_count system variable maximum value has been increased
from 1 million (1,048,576) to 4 million (4,194,304). The default value remains
unchanged at 16,382.
- MySQL 8.0 no longer supports building using wolfSSL. All MySQL builds now use
OpenSSL.
- The RE2 library is no longer used by MySQL. The library is no longer bundled
with source distributions and the WITH_RE2 CMake option is obsolete.
More Infos: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-18.html
A big thanks to @fluffy for his help with this update
MFH: 2020Q1
Security: fc91f2ef-fd7b-11e9-a1c7-b499baebfeaf
Sponsored by: Netzkommune GmbH
 |
Thursday, 19 Sep 2019
|
12:33 mmokhi
databases/mysql80-{client, server}: Update to latest release 8.0.17
This update includes security fixes on issues that are
mentioned on upstream critical patch report.
Further info:
https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html#AppendixMSQL
Delete upstream-merged patches
Change other local-patches according upstream changes
PR: 239272
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by: EuroBSDCon 2019 DevSummit
 |
Saturday, 11 May 2019
|
14:15 mmokhi
databases/mysql80-{client, server}: Update to latest release 8.0.16
This update includes:
Bugfixes:
- InnoDB: Undo tablespaces remained unencrypted after enabling
undo tablespace encryption at startup. (Bug #29477795)
- InnoDB: Problematic macros introduced with undo tablespace DDL support
(Bug #29324132, Bug #94243).
- InnoDB: Static thread local variables defined at the wrong scope
were not released at thread exit. (Bug #29305186)
- Memory leaks discovered in the innochecksum (Bug #28917614, Bug #93164).
New features:
- MySQL C API now supports asynchronous functions for
nonblocking communication with the MySQL server.
- MySQL now supports a new Chinese collation, utf8mb4_zh_0900_as_cs
- CMake now causes the build process to link with the llvm lld linker
for Clang if it is available.
Security Fix:
CVE-2019-2632, CVE-2019-2693, CVE-2019-2694, CVE-2019-2695 and other fixes.
More info:
https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html#AppendixMSQL
PR: 237399
Reported by: Brent Busby <brent@jfi.uchicago.edu>
Sponsored by: The FreeBSD Foundation
 |
Saturday, 26 Jan 2019
|
18:36 mmokhi
databases/mysql80-{client, server}: Update to latest release 8.0.14
This update (released on Jan 21st) includes:
Bugs Fixed:
Important Change: Fix importing a dump from a MySQL 5.7 server 8.0 failure.
(ER_WRONG_VALUE_FOR_VAR, when an unsupported [by 8.0] SQL mode was used).
The behavior of the server in such circumstances now depends on the setting
of the
`pseudo_slave_mode` system variable.
If this is false, the server rejects the mode setting with
ER_UNSUPPORTED_SQL_MODE.
Otherwise, server just gives a warning. (Bug #90337, Bug #27828236).
InnoDB: Properly initialize the static thread-local 'tables' variable in
the TempTable storage engine (on Solaris X86) was not properly initialized.
(Bug #28987365)
InnoDB: Fix incorrect lock order caused a deadlock when one thread attempted
to
drop a table while another created an encrypted tablespace. (Bug #28774259)
More info from upstream:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-14.html
While here, Adapt some local patches with new upstream changes.
PR: 234984
Sponsored by: The FreeBSD Foundation
 |
Saturday, 11 Aug 2018
|
20:22 mmokhi
databases/mysql80-{client, server}: Update ports to 8.0.12
This update includes Oracle Critical Patch Advisory published on July 2018
More info:
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixMSQL
Also:
Delete upstreamed hunks of patches.
Change local patches regarding upstream changes.
PR: 229861
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by: The FreeBSD Foundation
 |
Saturday, 12 May 2018
|
15:35 mmokhi
databases/mysql80-{client,server}: Upgrade the ports to GA version 8.0.11
Fix build with LibreSSL and OpenSSL-devel ports as well
MySQL 8.0.11 is the General Availability (GA) version of MySQL 8.
MySQL since this version supports FIPS-mode, if compiled using OpenSSL, AND
an OpenSSL library and FIPS Object Module are available at runtime.
FIPS mode imposes conditions on cryptographic operations such as
restrictions on acceptable encryption algorithms or requirements for longer
key lengths.
The --ssl-fips-mode client option enables control of FIPS mode on the client
side for:
mysql, mysqladmin, mysqlbinlog, mysqlcheck, mysqldump, mysqlimport,
mysqlpump, ...
This update includes bugfixes including (not limited to):
-InnoDB: The server was stopped before a fatal error message
was written to the error log.
-InnoDB: An incorrect GROUP BY result was returned when using the
TempTable storage engine and a NO PAD collation.
-InnoDB: The data retrieved from INFORMATION_SCHEMA.INNODB_COLUMNS was
incorrect for tables containing a virtual column.
Full Release-Notes are available at:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-11.html
 |
Saturday, 7 Jan 2017
|
20:34 lifanov
add databases/mysql80-server and databases/mysql80-client
This is a development snapshot of upcoming MySQL 8.0.
PR: 215738
Submitted by: Mahdi Mokhtari <mokhi64@gmail.com>
Reviewed by: matthew, feld
Approved by: matthew (mentor), feld
Differential Revision: https://reviews.freebsd.org/D9031
 |
Number of commits found: 14 |