15:52 Jochen Neumeister (joneum) 

databases/mysql80-{client, server}: Update to latest release 8.0.33

Bugs Fixed

    NDB Cluster: Occasional temporary errors which could occur when
opening a table from the NDB dictionary while repeatedly performing
concurrent schema operations were not retried. (Bug #34843889)

    NDB Cluster: During iteration, ordered index scans retain a cursor
position within each concurrently scanned ordered index fragment.
Ordered index fragments are modified and balanced as a result of
committing DML transactions, which can require scan cursors to be moved
within the tree. When running with query threads configured
(AutomaticThreadConfig set to 1), multiple threads can access the same
index fragment tree structure, and the scans of multiple threads can
have their cursors present in the same structure.

    The current issue arose due to an assumption in the logic for moving
scan cursors when committing DML operations that all scan cursors
belonged to the LDM thread owning the index fragment, which did not
allow for the possibility that such fragments might belong to query
threads. (Bug #33379702)

    References: See also: Bug #32257063.

    InnoDB: Dead code removal. (Bug #35036850, Bug #109873)

    InnoDB: Error messages related to innodb_doublewrite moved to the
error log. (Bug #34883045, Bug #109330)

    InnoDB: Prevent online DDL operations from accessing out-of-bounds
memory. (Bug #34750489, Bug #108925)

    InnoDB: ALTER TABLE ... AUTO_INCREMENT could be set to less than MAX
+ 1 and not forced to MAX + 1. (Bug #33419246, Bug #105092)

    InnoDB: Innodb_data_pending_fsyncs could show extremely high
inaccurate values because of a variable overflow. (Bug #30133150)

    Partitioning: Some IN() queries on partitioned tables were not
always handled correctly. (Bug #34801284)

    References: This issue is a regression of: Bug #32311183.

    Partitioning: Queries using the INDEX_MERGE optimizer hint was not
handled correctly in all cases. (Bug #34797257)

    Replication: XA transactions whose XIDs contained null bytes could
not be recovered. (Bug #34918985)

    Replication: When binlog_order_commits was set equal to 1, for any
two transactions and for any sub-step of the commit phase, the
transaction that was written to the binary log first did not always
execute the sub-step first, as expected. (Bug #34703698)

    Replication: Some binary log events were not always handled
correctly. (Bug #34617506)

    Replication: The binary log recovery process did not report all
possible error states. (Bug #33658850)

    Replication: Following CHANGE REPLICATION SOURCE TO
SOURCE_CONNECTION_AUTO_FAILOVER=1, failover generated a number of
misleading warnings in the log that implied there were problems when in
fact conditions were those expected for such a failover. These log
messages have been updated accordingly. (Bug #32135376)

    Replication: When a transaction failed, as a side effect, extraneous
error messages relating the replication data repositories were written
to the log. Now in such cases, we suppress such error messages, which
are not directly related to the issue of the failed transaction or its
cause. (Bug #19820134)

    Replication: Setting binlog_order_commits to OFF could lead to a
missed GTID in the next binary log file's Previous_gtids event.

    Our thanks to Yewei Xu and the Tencent team for the contribution.
(Bug #109485, Bug #34930969)

    Replication: Corrected the SQL statements suggested in the error
message text for ER_RPL_REPLICA_ERROR_RUNNING_QUERY.

    Our thanks to Dan McCombs for the contribution. (Bug #109154, Bug

    Replication: A hash scan builds a hash of changes, scans the target
table or index, and applies any matching change for the current entry.
In the build phase, it uses only the before image, and skips any after
image. Problems arose in some cases because generated columns were
computed for the (skipped) after image, leading to replication errors.
This is fixed by not computing generated columns any longer for
seek-only calls such as hash scans.

    Our thanks to dc huang for the contribution. (Bug #107366, Bug

    Replication: In certain rare cases, it was possible to set
gtid_mode=OFF for one session while another session, after
WAIT_FOR_EXECUTED_GTID_SET() was issued by a user in this second
session, was still waiting for the next GTID set from the first session.
This could result in the second session waiting indefinitely for the
function to return. (Bug #99921, Bug #31505993)

    Group Replication: Accessing the Performance Schema
replication_group_communication_information and
replication_group_member_stats tables in parallel sometimes caused
subsequent group replication operations to hang. (Bug #34870181)

    Group Replication: In certain cases, the group replication secondary
node unexpectedly shut down while purging the relay log. (Bug #34397106)

    Group Replication: When shutting down the Group Replication plugin,
the order in which the associated events were reported the error log
sometimes led to confusion. To remove any doubts, we now make sure that
Plugin group_replication reported: 'Plugin 'group_replication' has been
stopped. is in fact the last log message relating to the shutdown,
written only when all other events associated with shutting down the
plugin have been logged. (Bug #109345, Bug #34887491)

    Microsoft Windows: The authentication_fido_client plugin stopped
responding during the authentication process if it was unable to find a
FIDO device on the Windows client host. (Bug #34918044)

    In certain cases, CONVERT(utf8mb3_column USING UTF16) was rejected
with the error Cannot convert string '\x--...' from binary to utf16.
(Bug #35129361)

    When joining two tables on a string column, and the column from one
of the tables has an additional predicate comparing it with a temporal
literal, constant propagation in some cases incorrectly caused the join
condition to be modified such that it used temporal rather than string
semantics when comparing the strings. This caused incorrect results to
be returned from the join. (Bug #35115909)

    Error messages returned after calling the mysql_reset_connection() C
API function in a prepared statement did not identify the function name
properly. (Bug #35107280)

    Fixed a regression in a previous fix for an issue with windowing
functions.

    Our thanks to Dmitry Lenev for the contribution. (Bug #35061924)

    References: This issue is a regression of: Bug #34572136.

    When replacing subqueries in transforms, the internal flag showing
whether a given query block contains any subqueries (PROP_SUBQUERY) was
not updated afterwards. (Bug #35060385)

    A client setting the character set to an impermissible client
character set (ucs2, utf16, utf16le, or utf32) could cause unexpected
behavior when the client used an authentication plugin. (Bug #35054579)

Changelog:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-33.html

Sponsored by:	Netzkommune GmbH

    9fd5647

17:51 Jochen Neumeister (joneum) 

databases/mysql80-*: Unbreak on i386

Fix a issue with i386:
--yplg_out: protoc-gen-yplg: Plugin killed by signal 11.
*** Error code 1

PR: 269203
Sponsored by: Netzkommmune GmbH

    6498bc6

14:34 Jochen Neumeister (joneum) 

databases/mysql80-*: Update to latest release 8.0.30

PR:	265468

Bugs Fixed:
- InnoDB: A TRUNCATE TABLE operation failed to remove data dictionary entries
for columns that were dropped using ALGORITHM=INSTANT.
- InnoDB: An incorrect nullable column calculation on tables with instantly
added columns caused data to be interpreted incorrectly
- InnoDB: The read_2_bytes() function in the InnoDB sources, which reads bytes
from the log buffer, returned a null pointer.
- Replication: The COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE column in the
Performance Schema table replication_group_member_stats could persistently show
transactions related to view change events (View_change_log_event) that had
already been applied. These events are queued in the Group Replication applier
channel but applied in the Group Replication recovery channel, causing a race
condition that could result in the counter decrement being lost. The increment
of the count now takes place at a more suitable point, and the counter for
COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE is also now set to zero when the
applier is not busy.
- Debug MySQL binaries can now be built using -0g and -fno-inline.

See full Changelog here:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html

Sponsored by:	Netzkommune GmbH

    b5daf80

06:49 Loïc Bartoletti (lbartoletti) 

databases/mysql*: fix pkg-plist use share/man

Approved by:	portmgr (blanket)

    9f0ff92

15:32 Jochen Neumeister (joneum) 

databases/mysql80-*: Update to 8.0.28

Changelog: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html

Sponsored by:	Netzkommune GmbH

    b8d235ae

17:23 Jochen Neumeister (joneum) 

databases/mysql80-client: Fix a Problem with FIDO Option

there was an error, are both options turned off

PR:	260080
Sponsored by:	Netzkommune GmbH

    b566b31

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

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

10:29 joneum 

There is a problem, when mysql80 build with openssl and ZLIB = ON

-- Installing:
/usr/ports/databases/mysql80-client/work/stage/usr/local/man/man1/zlib_decompress.1
====> Compressing man pages (compress-man)
===>   Installing ldconfig configuration file
===>  Installing for mysql80-client-8.0.19_1
===>  Checking if mysql80-client is already installed
===>   Registering installation for mysql80-client-8.0.19_1 as automatic
pkg-static: Unable to access file
/usr/ports/databases/mysql80-client/work/stageusr/local/bin/zlib_decompress:No
such file or directory
*** Error code 74

This fix the problem

PR:		228234
Sponsored by:	Netzkommune GmbH

 

20:06 joneum 

databases/mysql80-{client, server}: Update to latest release 8.0.19

- New FPROFILE_GENERATE and FPROFILE_USE CMake options are available for
experimenting with profile guided optimization (PGO) with GCC. See the
cmake/fprofile.cmake in a MySQL source distribution for information about using
them. These options have been tested with GCC 8 and 9, and with Clang.
- Enabling FPROFILE_USE also enables WITH_LTO (link time optimization).
- Innodb_system_rows_read, Innodb_system_rows_inserted,
Innodb_system_rows_deleted status variables were added for counting row
operations on InnoDB tables that belong to system-created schemas. The new
status variables are similar to the existing Innodb_rows_read,
Innodb_rows_inserted, Innodb_rows_deleted status variables, which count
operations on InnoDB tables that belong to both user-created and system-created
schemas.
- The new status variables are useful in replication environments where
relay_log_info_repository and master_info_repository variables are set to TABLE,
resulting in higher row operation counts on slaves due to operations performed
on the slave_master_info, slave_replay_log_info, and slave_worker_info tables,
which belong to the system-created mysql schema. For a valid comparison of
master and slave row operation counts, operations on tables in system-created
schemas can now be excluded using the count data provided by the new status
variables.

More infos: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-19.html

Submitted by:	fluffy
Approved by:	mmokhi (maintainer, implicit)
Sponsored by:	Netzkommune GmbH

 

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

 

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

 

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

 

15:44 mmokhi 

databases/mysql80-{server, client}: Update port to the latest release 8.0.2
Changes happened into format of --version which caused r450384

Reviewed by:	mat (mentor)
Approved by:	mat (mentor)
Sponsored by:	Netzkommune GmbH
Differential Revision:	https://reviews.freebsd.org/D12579

 

16:06 lifanov 

add new includes for MySQL 8.0 client

PR:		215903
Submitted by:	Mahdi Mokhtari <mokhi64@gmail.com> (maintainer)
Reviewed by:	matthew
Approved by:	matthew (mentor)
Differential Revision:	https://reviews.freebsd.org/D9100

 

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