head 1.12; access; symbols pkgsrc-2022Q4:1.11.0.28 pkgsrc-2022Q4-base:1.11 pkgsrc-2022Q3:1.11.0.26 pkgsrc-2022Q3-base:1.11 pkgsrc-2022Q2:1.11.0.24 pkgsrc-2022Q2-base:1.11 pkgsrc-2022Q1:1.11.0.22 pkgsrc-2022Q1-base:1.11 pkgsrc-2021Q4:1.11.0.20 pkgsrc-2021Q4-base:1.11 pkgsrc-2021Q3:1.11.0.18 pkgsrc-2021Q3-base:1.11 pkgsrc-2021Q2:1.11.0.16 pkgsrc-2021Q2-base:1.11 pkgsrc-2021Q1:1.11.0.14 pkgsrc-2021Q1-base:1.11 pkgsrc-2020Q4:1.11.0.12 pkgsrc-2020Q4-base:1.11 pkgsrc-2020Q3:1.11.0.10 pkgsrc-2020Q3-base:1.11 pkgsrc-2020Q2:1.11.0.8 pkgsrc-2020Q2-base:1.11 pkgsrc-2020Q1:1.11.0.4 pkgsrc-2020Q1-base:1.11 pkgsrc-2019Q4:1.11.0.6 pkgsrc-2019Q4-base:1.11 pkgsrc-2019Q3:1.11.0.2 pkgsrc-2019Q3-base:1.11 pkgsrc-2019Q2:1.10.0.6 pkgsrc-2019Q2-base:1.10 pkgsrc-2019Q1:1.10.0.4 pkgsrc-2019Q1-base:1.10 pkgsrc-2018Q4:1.10.0.2 pkgsrc-2018Q4-base:1.10 pkgsrc-2018Q3:1.9.0.2 pkgsrc-2018Q3-base:1.9 pkgsrc-2018Q2:1.8.0.2 pkgsrc-2018Q2-base:1.8 pkgsrc-2018Q1:1.7.0.2 pkgsrc-2018Q1-base:1.7 pkgsrc-2017Q4:1.6.0.6 pkgsrc-2017Q4-base:1.6 pkgsrc-2017Q3:1.6.0.4 pkgsrc-2017Q3-base:1.6 pkgsrc-2017Q2:1.4.0.2 pkgsrc-2017Q2-base:1.4 pkgsrc-2017Q1:1.3.0.2 pkgsrc-2017Q1-base:1.3 pkgsrc-2016Q4:1.2.0.2 pkgsrc-2016Q4-base:1.2 pkgsrc-2016Q3:1.1.0.2 pkgsrc-2016Q3-base:1.1; locks; strict; comment @# @; 1.12 date 2023.02.01.16.38.12; author jperkin; state dead; branches; next 1.11; commitid I79QKoL3NvDkgQbE; 1.11 date 2019.07.01.10.25.49; author adam; state Exp; branches; next 1.10; commitid iQVcFDyvvjm3nktB; 1.10 date 2018.12.13.19.51.45; author adam; state Exp; branches 1.10.6.1; next 1.9; commitid XjJhLcEnCzYFVF3B; 1.9 date 2018.08.16.16.06.09; author adam; state Exp; branches; next 1.8; commitid L6GYByfYsnXGumOA; 1.8 date 2018.04.29.21.44.12; author adam; state Exp; branches; next 1.7; commitid sHIO4GAaXEhgSnAA; 1.7 date 2018.01.01.21.18.18; author adam; state Exp; branches; next 1.6; commitid VDVceOVT4khVwdlA; 1.6 date 2017.09.13.17.34.41; author adam; state Exp; branches; next 1.5; commitid c0wj42Xh3xQaP37A; 1.5 date 2017.09.01.10.02.01; author abs; state Exp; branches; next 1.4; commitid N0De1Va6y11YHt5A; 1.4 date 2017.04.30.05.10.32; author adam; state Exp; branches; next 1.3; commitid osWjdso3nttg5wPz; 1.3 date 2017.01.01.16.06.07; author adam; state Exp; branches; next 1.2; commitid jkBZ9Kd0NEyexhAz; 1.2 date 2016.10.14.19.28.28; author adam; state Exp; branches; next 1.1; commitid 2V2VXJYmwTeWb9qz; 1.1 date 2016.09.16.06.49.11; author adam; state Exp; branches; next ; commitid bzWTDZHvVHlQStmz; 1.10.6.1 date 2019.08.10.13.12.45; author bsiegert; state Exp; branches; next ; commitid 5LUiSaHLKZEu0uyB; desc @@ 1.12 log @mysql57: Update to 5.7.41. pkgsrc change: switch to bundled boost, this older release series no longer builds against the latest pkgsrc version of boost. Changes in MySQL 5.7.41 (2023-01-17, General Availability) Compilation Notes * Upgraded the bundled lz4 library from version 1.9.3 to version 1.9.4. (Bug #34809802) Functionality Added or Changed * Important Change: The linked OpenSSL library for MySQL Server has been updated to version 1.1.1s. Issues fixed in OpenSSL version 1.1.1s are described at https://www.openssl.org/news/cl111.txt. (Bug #34828308) * The linked curl library for MySQL Server (Enterprise Edition) has been updated to version 7.86.0. (Bug #34828111) Bugs Fixed * Replication: Issuing STOP SLAVE SQL_THREAD while the SQL thread was handling a transaction caused replication to stop immediately, instead of waiting 60 seconds for the event group to complete before shutting down the SQL thread as expected. The root cause of this issue was due to the internal variable storing the last event start time not being reset after the SQL thread was restarted. We fix this by resetting the variable holding the last event start time whenever the SQL thread is started. (Bug #33646899) * Replication: The relay_log_space_limit system variable is a 64-bit value, but its valid maximum was specified internally as that of a 32-bit value. (Bug #106323, Bug #33799840) * Some remote connections to the server were not handled correctly. This issue arose as the result of a previous fix for an issue with require_secure_transport. (Bug #34857411) References: This issue is a regression of: Bug #34094706. * The linked OpenLDAP library for MySQL Server (Enterprise edition) was updated to version 2.5.13. (Bug #34815046) * The bundled zlib library has been upgraded to zlib 1.2.13; zlib 1.2.13 is now the minimum zlib version supported. (Bug #34711762) * Stack overruns could be erroneously reported when using the thread pool under heavy load. The race condition causing this in the thread pool has been avoided with an additional thread group ID check. (Bug #34414959) * The data and the GTIDs backed up by mysqldump were inconsistent when the options --single-transaction and --set-gtid-purged=ON were both used. It was because GTID_EXECUTED was fetched at the end of the dump, at which point the GTIDs on the server could have increased already. With this fixed, a FLUSH TABLES WITH READ LOCK is performed at the beginning of the dump and GTID_EXECUTED was fetched right after, to ensure its value is consistent with the snapshot taken by mysqldump. Our thanks to Marcelo Altmann for the contribution. (Bug #33630199) * In prepared statements, some types of subqueries could cause a server exit. (Bug #33100586) * The audit_log server-side plugin always logged an entire multiple query, rather than logging only the specific part of the query that was executed. Changing when the query length is set resolves the issue. (Bug #107390, Bug #34207811) @ text @$NetBSD: patch-cmake_boost.cmake,v 1.11 2019/07/01 10:25:49 adam Exp $ Allow newer Boost. --- cmake/boost.cmake.orig 2019-04-13 13:32:15.000000000 +0000 +++ cmake/boost.cmake @@@@ -262,12 +262,7 @@@@ IF(NOT BOOST_MAJOR_VERSION EQUAL 10) COULD_NOT_FIND_BOOST() ENDIF() -IF(NOT BOOST_MINOR_VERSION EQUAL 59) - MESSAGE(WARNING "Boost minor version found is ${BOOST_MINOR_VERSION} " - "we need 59" - ) - COULD_NOT_FIND_BOOST() -ENDIF() + MESSAGE(STATUS "BOOST_INCLUDE_DIR ${BOOST_INCLUDE_DIR}") @ 1.11 log @mysql57-client: allow newer Boost; fixes building with boost-1.70.0 @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.10 2018/12/13 19:51:45 adam Exp $ @ 1.10 log @revbump for boost 1.69.0 @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.9 2018/08/16 16:06:09 adam Exp $ d3 1 a3 1 Fix to use a newer version of Boost. d5 1 a5 1 --- cmake/boost.cmake.orig 2017-06-22 14:13:19.000000000 +0000 d7 1 a7 32 @@@@ -13,7 +13,7 @@@@ # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA -# We want boost 1.59.0 in order to build our boost/geometry code. +# We want boost 1.69.0 in order to build our boost/geometry code. # The boost tarball is fairly big, and takes several minutes # to download. So we recommend downloading/unpacking it # only once, in a place visible from any bzr sandbox. @@@@ -31,10 +31,10 @@@@ # we assume that the correct version (see below) # is installed on the compile host in the standard location. -SET(BOOST_PACKAGE_NAME "boost_1_59_0") +SET(BOOST_PACKAGE_NAME "boost_1_69_0") SET(BOOST_TARBALL "${BOOST_PACKAGE_NAME}.tar.gz") SET(BOOST_DOWNLOAD_URL - "http://sourceforge.net/projects/boost/files/boost/1.59.0/${BOOST_TARBALL}" + "http://sourceforge.net/projects/boost/files/boost/1.69.0/${BOOST_TARBALL}" ) SET(OLD_PACKAGE_NAMES "boost_1_55_0 boost_1_56_0 boost_1_57_0 boost_1_58_0") @@@@ -244,7 +244,7 @@@@ ENDIF() # // BOOST_VERSION % 100 is the patch level # // BOOST_VERSION / 100 % 1000 is the minor version # // BOOST_VERSION / 100000 is the major version -# #define BOOST_VERSION 105900 +# #define BOOST_VERSION 106900 FILE(STRINGS "${BOOST_INCLUDE_DIR}/boost/version.hpp" BOOST_VERSION_NUMBER REGEX "^#define[\t ]+BOOST_VERSION[\t ][0-9]+.*" @@@@ -262,9 +262,9 @@@@ IF(NOT BOOST_MAJOR_VERSION EQUAL 10) d12 1 a12 2 +IF(NOT BOOST_MINOR_VERSION EQUAL 69) MESSAGE(WARNING "Boost minor version found is ${BOOST_MINOR_VERSION} " d14 7 a20 4 + "we need 69" ) COULD_NOT_FIND_BOOST() ENDIF() @ 1.10.6.1 log @Pullup ticket #6029 - requested by taca databases/mysql57-client, databases/mysql57-server: security fix Revisions pulled up: - databases/mysql57-client/Makefile 1.24 - databases/mysql57-client/Makefile.common 1.20 - databases/mysql57-client/PLIST 1.14 - databases/mysql57-client/distinfo 1.30-1.31 - databases/mysql57-client/patches/patch-cmake_boost.cmake 1.11 - databases/mysql57-server/Makefile 1.24 - databases/mysql57-server/PLIST 1.13 --- Module Name: pkgsrc Committed By: ryoon Date: Mon Jul 1 04:08:55 UTC 2019 Modified Files: pkgsrc/databases/mysql57-client: Makefile pkgsrc/databases/mysql57-server: Makefile Log Message: Recursive revbump from boost-1.70.0 --- Module Name: pkgsrc Committed By: adam Date: Mon Jul 1 10:25:49 UTC 2019 Modified Files: pkgsrc/databases/mysql57-client: distinfo pkgsrc/databases/mysql57-client/patches: patch-cmake_boost.cmake Log Message: mysql57-client: allow newer Boost; fixes building with boost-1.70.0 --- Module Name: pkgsrc Committed By: adam Date: Tue Aug 6 06:56:43 UTC 2019 Modified Files: pkgsrc/databases/mysql57-client: Makefile Makefile.common PLIST distinfo pkgsrc/databases/mysql57-server: Makefile PLIST Log Message: mysql57: updated to 5.7.27 Changes in MySQL 5.7.27: Keyring Notes The keyring_aws plugin has been updated to use the latest AWS SDK and so that it works with OpenSSL 1.1. Packaging Notes Binary packages that include curl rather than linking to the system curl library now use curl 7.64.0. X Plugin Notes On Windows, X Plugin logged some messages that were unnecessary or insufficiently informative. The messages have been removed or improved as appropriate. Functionality Added or Changed Microsoft Windows: A new warning message now reminds DBAs that connections made using the MySQL named pipe on Windows has limited the permissions a connector can request on the named pipe. Previously, the named_pipe_full_access_group system variable was set to a value that maps to the built-in Windows Everyone group (SID S-1-1-0) by default. However, this group is not ideal and should be replaced with a group that restricts its membership for connectors that are unable to request fewer permissions on the MySQL named pipe. The new warning is written to the error log at startup if the string value assigned to named_pipe_full_access_group is '*everyone*' (or the Windows System Language equivalent) and named pipes are enabled. In addition, the warning is written to the error log and raised to the client if the system variable is reset to the Everyone group at runtime. Bugs Fixed InnoDB: Insufficient memory barriers in the rw-lock implementation caused deadlocks on ARM. Thanks to Yibo Cai from Arm Technology for the contribution. InnoDB: Manually changing the system time while the MySQL server was running caused page cleaner thread delays. InnoDB: During log application, after an OPTIMIZE TABLE operation, InnoDB did not populate virtual columns before checking for virtual column index updates. InnoDB: An INSERT operation involving a generated virtual BLOB column resulted a secondary index being updated with an incorrect value. InnoDB: A full-text cache lock taken when data is synchronized was not released if the full-text cache size exceeded the full-text cache size limit. InnoDB: Client sessions using different auto_increment_increment values while performing concurrent insert operations could cause a duplicate key error. Partitioning: ALTER TABLE ... EXCHANGE PARTITION failed with the error Non matching attribute 'ROW_FORMAT' between partition and table when the partitioned table had partitions using different row formats, even when the partition to be exchanged used the same row format as the non-partitioned table. Replication: The error message that is issued for a discrepancy between the number of group members and the auto-increment interval incorrectly referred to the group_replication_auto_increment_increment system variable, instead of the auto_increment_increment system variable. The value of auto_increment_increment is changed to the value specified by group_replication_auto_increment_increment when Group Replication starts, but only if auto_increment_increment and auto_increment_offset have their default values, and from MySQL 8.0, only in multi-primary mode. The value of auto_increment_increment was always the value that was checked for the error message, and it has now been corrected to give the accurate system variable name. Replication: When events generated by one MySQL server instance were written to the binary log of another instance, the second server implicitly assumed that the first server supported the same number of binary log event types as itself. Where this was not the case, the event header was handled incorrectly. The issue has now been fixed. Thanks to Facebook for the contribution. Replication: In Group Replication, joining members could wrongly identify themselves as incompatible with an existing replication group even if there were members at the same version already in the group, because they checked against all other members, including the member at the highest version. Joining members also included their own version in the compatibility check. Now, joining members only compare themselves with the existing group member at the lowest version, and do not count their own version. Replication: If a FLUSH LOGS statement was issued before the binary log file was initialized, the statement attempted to write a binary log rotation event to the uninitialized file. The server now checks first that a binary log file is available. Replication: When a MEMORY table is implicitly deleted on a master following a server restart, the master writes a DELETE statement to the binary log so that slaves also empty the table. This generated event now includes a comment in the binary log so that the reason for the DELETE statement is easy to identify. Thanks to Daniël van Eeden for the contribution. Replication: With statement-based replication in use, if super_read_only was set to ON for a server at the point when a no-op transaction was between its UPDATE and COMMIT operations, the transaction was written to the binary log and assigned a GTID. The transaction is now blocked in this situation. From MySQL 8.0, the value of super_read_only cannot be changed while a transaction is in progress. Replication: The group communication engine for Group Replication (XCom, a Paxos variant) did not handle out of memory errors in an appropriate way. If memory could not be allocated to make a copy of the payload for a message, an error was logged but the message was still sent, with a null payload. The Group Communication System (GCS) on the receiving member discarded the message as empty, and the XCom instance on the receiving member accepted this action and did not retry, resulting in the message effectively being skipped. This caused the GTID set on the receiving member to diverge from the group, leading to replication errors. XCom now terminates gracefully if it experiences an out of memory error, so that this situation cannot occur. Replication: In query log events in the binary log, the thread ID used for the execution of DROP TABLE and DELETE statements was identified incorrectly or not at all. On a multi-threaded replication slave, where temporary tables were involved (which require the correct thread ID as they are session specific), this omission resulted in errors when using mysqlbinlog to replay the binary log for point-in-time recovery. The thread ID is now set correctly. Replication: When a slave server logs master status and connection information to a table (master_info_repository=TABLE), which is the default in MySQL 8.0, the mysql.slave_master_info table was not being updated on shutdown if the server was in super read only mode (super_read_only=ON). No error was written to the error log at this time, but replication failed after server startup because the master log file and master log position information was out of date. The thread that updates the master info log at shutdown is now excluded from read-only checks like other replication threads are, so it can update the table even if the server is in super read only mode. Error handling for a slave that is shutting down has also been improved so that any failure to write to the slave status logs results in an error in the error log. An overly strict assertion could be raised during sorting of stored program local objects. Installing from RPM packages could result in an error log with incorrect permissions. Enabling audit log encryption could cause a server exit. On Debian and Ubuntu, MySQL packages did not enable mysql.service after upgrades from native MySQL packages. The server did not properly close shared-memory connections when an error occurred, which could result in unexpected server behavior. MySQL Installer did not install OpenSSL DLL dependencies if the Development component was not selected. The parser could leak memory for certain multiple-statement queries. CREATE USER and ALTER USER did not check the validity of a hashed authentication string when used with IDENTIFIED WITH auth_plugin AS 'hash_string' syntax. For InnoDB tables that contained an index on a VARCHAR column and were created prior to MySQL 5.7.23, some simple ALTER TABLE statements that should have been done in place were performed with a table rebuild after an upgrade to MySQL 5.7.23 or higher. HANDLER statements did not always work correctly with tables having generated columns. Session-tracking information in the client/server protocol could be mishandled. With the PAD_CHAR_TO_FULL_LENGTH SQL mode enabled, password changes failed, with no warning or error reported. The audit_log plugin did not log UNINSTALL PLUGIN audit_log statements. audit_log filtering operations could leak memory. An index defined on a virtual generated column could fail to be updated if the column had a base column in a foreign key relationship. Privileges for dropping some Performance Schema tables were checked incorrectly. A query that employed a derived table which included an ORDER BY was not always handled correctly. Base columns were not excluded from index-only access by a generated column. A thread pool group could be blocked when a thread process tick time exceeded the maximum permitted value. The tick time now uses a larger data type to permit larger values. MySQL does not support OpenSSL session tickets, but did not set the SSL_OP_NO_TICKET flag to inform OpenSSL of that. The flag is now set. The audit_null plugin did not properly check for a null event record. UpdateXML() did not always free memory properly in certain cases. Empty values in the name column of the mysql.plugin system table caused the server to exit during startup. With the thread_pool plugin enabled, the Performance Schema status_by_thread table contained no data. If 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). Inner tables of different semijoin nests were interleaved during materialization, which could lead to a different result for the same query when it used a different query plan. To keep this from occurring, a check is added to prevent such interleaving. A query involving GROUP BY on a TIMESTAMP column resulted in a duplicate entry for key (ER_DUP_ENTRY) error. This problem arose when TIMESTAMP values were inserted into a table using a given setting for the time zone and these values were later fetched after the time zone setting had been changed, such that at least some of the inserted TIMESTAMP values occurred during the hour that the time changed from standard to daylight time (DST) in the new time zone, during which time the same TIMESTAMP value can exist twice. Now, when the server would otherwise return the error DUPLICATE ENTRY FOR KEY 'group_key', if the grouping involves a TIMESTAMP column, it instead raises the error Grouping on temporal is non-deterministic for time zones having DST. Please consider switching to UTC for this query. In addition, it is suggested to set explicit_defaults_for_timestamp to ON as well as one or more of MODE_NO_ZERO_IN_DATE, MODE_NO_ZERO_DATE, or MODE_INVALID_DATES as part of the server SQL mode to help avoid this issue. @ text @d1 1 a1 1 $NetBSD$ d3 1 a3 1 Allow newer Boost. d5 1 a5 1 --- cmake/boost.cmake.orig 2019-04-13 13:32:15.000000000 +0000 d7 32 a38 1 @@@@ -262,12 +262,7 @@@@ IF(NOT BOOST_MAJOR_VERSION EQUAL 10) d43 2 a44 1 - MESSAGE(WARNING "Boost minor version found is ${BOOST_MINOR_VERSION} " d46 4 a49 7 - ) - COULD_NOT_FIND_BOOST() -ENDIF() + MESSAGE(STATUS "BOOST_INCLUDE_DIR ${BOOST_INCLUDE_DIR}") @ 1.9 log @mysql57: updated to 5.7.23 5.7.23: Functionality Added or Changed Previously, for the --ssl-mode=VERIFY_IDENTITY or --ssl-verify-server-cert option, the client checked whether the host name that it used for connecting matched the Common Name value in the certificate but not the Subject Alternative Name value. Now, if the client uses OpenSSL 1.0.2 or higher, the client checks whether the host name matches either the Subject Alternative Name value or the Common Name value in the server certificate. Thanks to Daniël van Eeden for a patch on which this change was based. Bugs Fixed Important Change; Partitioning: After creating partitioned InnoDB tables with very long names, the table_name columns in the corresponding entries in the mysql.innodb_index_stats and mysql.innodb_table_stats system tables were truncated. To fix this issue, the length of the table_name column in each of these tables has been increased from 64 to 199 characters. In both cases, this is now the same as the lengths of these columns in MySQL 8.0. InnoDB: The ngram full-text search parser permitted comma and period characters to be tokenized as words, which caused an inconsistency between boolean and natural language mode search results. Comma and period characters are no longer tokenized. InnoDB: An I/O error returned by an fsync() operation is now treated as a hard error. InnoDB: A schema mismatch error reported during an import tablespace operation failed to print mismatched table flags in a readable format. InnoDB: A DDL operation failed to wait for a FULLTEXT index optimization operation to finish. InnoDB: An unnecessary check for read-only transactions was removed from the trx_set_rw_mode() function. Thanks to Sandeep Sethia for the patch. InnoDB: A DDL operation that added a foreign key constraint raised an assertion when it accessed a stale memory object that belonged to the parent table. InnoDB: A DDL operation on a table with a FULLTEXT index during full-text index cache synchronization caused an assertion failure. InnoDB: A failing assertion occurred after initiating a memcached get operation. InnoDB: A corrupt index ID encountered during a foreign key check raised an assertion. InnoDB: An internal deadlock during a DDL operation resulted in a long semaphore wait followed by a server exit. InnoDB: A DDL operation encountered a serious error due to an invalid lock upgrade. InnoDB: On a Windows 64-bit system, invalid buffer pool configuration values caused the server to exit on startup. Partitioning: For a partitioned table, partition update time could be incorrect after rebuilding the table or restarting the server. Partitioning: An extraneous row lock was imposed by an update to a partitioned InnoDB table. Replication: The log messages generated when a member fails to join the group have been improved, for example when group_replication_group_name on the member joining the group does not match the seed's group_replication_group_name this is now described in the log message. Replication: The ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY error was being logged incorrectly. Replication: The use of replication filters or binary log filters can cause issues when they are applied to tables that are updated with XA transactions. Filtering of tables could cause an XA transaction to be empty on a replication slave, and empty XA transactions are not supported. Also, with the settings master_info_repository=TABLE and relay_log_info_repository=TABLE on a replication slave, which became the defaults in MySQL 8.0, the internal state of the data engine transaction is changed following a filtered XA transaction, and can become inconsistent with the replication transaction context state. Due to these issues, the use of replication filters or binary log filters in combination with XA transactions is not supported. This fix adds the new error ER_XA_REPLICATION_FILTERS, which is logged whenever an XA transaction is impacted by a replication filter, whether or not the transaction was empty as a result. If the transaction is not empty, the replication slave is able to continue running, but you should take steps to discontinue the use of replication filters with XA transactions in order to avoid potential issues. If the transaction is empty, the replication slave stops. In that event, the replication slave might be in an undetermined state in which the consistency of the replication process might be compromised. In particular, the gtid_executed set on a slave of the slave might be inconsistent with that on the master. To resolve this situation, isolate the master and stop all replication, then check GTID consistency across the replication topology. Undo the XA transaction that generated the error message, then restart replication. Replication: When a transaction larger than the binary log transaction cache size (binlog_cache_size) was flushed to a temporary file during processing, and the flush failed due to a lack of space in the temporary directory, the flush error was not handled correctly. No message was written to the error log, and the binary log cache was not cleared after the transaction was rolled back. Now, in this situation, the server takes an appropriate action based on the binlog_error_action setting (shut down the server or halt logging), and writes a message to the error log. When the transaction is rolled back, the server checks for flush errors and clears the binary log cache if any occurred. Replication: Using an IP address or hostname in any Group Replication related configuration on macOS was failing. Replication: When GTIDs are in use for replication, replicated transactions that are filtered out on the slave are persisted. If binary logging is enabled on the slave, the filtered-out transaction is written to the binary log as a Gtid_log_event followed by an empty transaction containing only BEGIN and COMMIT statements. If binary logging is disabled, the GTID of the filtered-out transaction is written to the mysql.gtid_executed table. This process ensures that there are no gaps in the set of executed GTIDs, and that the filtered-out transactions are not retrieved again if the slave reconnects to the master. Previously, this process was not done for CREATE DATABASE, ALTER DATABASE, and DROP DATABASE statements, but it is now carried out for those statements as well as for others. Replication: On a multithreaded slave, when a STOP SLAVE statement is executed on the slave, followed by a START SLAVE statement, the error log can report a different position in the binary log for the slave SQL thread when exiting, compared to the position reported for the slave SQL thread at the subsequent initialization. For a multithreaded slave, the position reported for the SQL thread on exit is a low water mark, up to which the replication stream is consistent and has no gaps. Transactions appearing before the position are guaranteed to have committed, but transactions after the position may have committed or not. However, this low water mark was being reported before the process to stop the worker threads was actually carried out, and the low water mark was subsequently updated by a checkpoint routine during that process. The timing of the log message has now been changed so that the final low water mark is reported as the position for the SQL thread on exit. Replication: In certain situations, such as during distributed recovery procedure, the certification info garbage collection was purging more data than it should, resulting in conflicts not being detected. The garbage collection procedure has been improved to take this case in consideration. Replication: When the group_replication_applier channel's applier thread encountered an error, the master_log_name and end_log_pos in the error message were incorrect. In Group Replication, the events of a transaction are replicated before they are written to the binary log of the member where the transaction originated. The result is that the final master_log_name and the end_log_pos of those events are unknown at the time they are applied on the replica by group_replication_applier channel's applier thread. To avoid confusion, now any such error messages encountered by a group_replication_applier channel do not contain the binary log name and the binary log position. A heap overflow vulnerability in the MySQL client library was fixed. For generated columns that used the INTERVAL() function, incorrect behavior could occur. The exec_in_background command for mysqltest is now available in MySQL 5.7. An unencrypted connection could result from a client connection attempt specifying that an encrypted connection was required, if the server was not configured to support SSL. A BETWEEN clause comparing negative values could lead to erroneous results. Audit log filter rules did not permit class names to be specified as an array of strings. @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.8 2018/04/29 21:44:12 adam Exp $ d12 1 a12 1 +# We want boost 1.68.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_68_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.68.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106800 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 68) d46 1 a46 1 + "we need 68" @ 1.8 log @mysql57: updated to 5.7.22 Changes in MySQL 5.7.22: Deprecation and Removal Notes These compatibility SQL modes are now deprecated and will be removed in MySQL 8.0: DB2, MAXDB, MSSQL, MYSQL323, MYSQL40, ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, NO_KEY_OPTIONS, NO_TABLE_OPTIONS. These deprecations have two implications: Assigning a deprecated mode to the sql_mode system variable produces a warning. With the MAXDB SQL mode enabled, using CREATE TABLE or ALTER TABLE to add a TIMESTAMP column to a table produces a warning. Statements that use these deprecated SQL modes may fail when replicated from a MySQL 5.7 master to a MySQL 8.0 slave, or may have different effects on master and slave. To avoid such problems, applications that use the modes deprecated in MySQL 5.7 should be revised not to use them. Test Suite Notes Reduction of compiler and platform differences in GIS handling of floating-point results enables simplification of related test cases that no longer need rounding to avoid spurious test failures. X Plugin Notes X Plugin connection attempts using the X Protocol did not return an error when the default database specified in the connection options was invalid, and the connection was allowed with a null default database. Connection attempts using the classic MySQL protocol did return an error and disallowed the connection. X Protocol connection attempts now also disallow the connection if an invalid schema is specified. Functionality Added or Changed Replication: Changes introduced in version 8 which enable XCom to identify members using the concept of an incarnation have been merged in to version 5.7. These underlying changes add a UUID to members each time they join a group and this information can be used to distinguish among different member incarnations. Replication: It is now possible to specify whether information written into the binary log enables replication slaves to parallelize based on commit timestamps, or on transaction write sets. JSON: The JSON_MERGE() function is renamed to JSON_MERGE_PRESERVE(). JSON: Added the JSON utility function JSON_PRETTY(), which prints an existing JSON value, or any string that can successfully be parsed as a JSON document, in a format that can be easily read by humans. Each JSON object member or array value is displayed on a separate line of the output; each child object or array is intended 2 spaces with respect to its parent. Bugs Fixed @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.7 2018/01/01 21:18:18 adam Exp $ d12 1 a12 1 +# We want boost 1.67.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_67_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.67.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106700 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 67) d46 1 a46 1 + "we need 67" @ 1.7 log @Revbump after boost update @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.6 2017/09/13 17:34:41 adam Exp $ d12 1 a12 1 +# We want boost 1.66.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_66_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.66.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106600 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 66) d46 1 a46 1 + "we need 66" @ 1.6 log @boost: update to 1.65.1 Fixes in 1.65.1 Config: * Version macro changes for CUDA. * Update last known MSVC version. * MSVC 14.11 supports structured bindings. Context: * Return a continuation from functions executed by resume_with. Fiber: * Return a continuation from functions executed by resume_with. Smart Pointers: * Fix Visual C++ version checks. * Fix compilation for NVCC with host compiler clang. Stacktrace: * Update build testing file to detail with a MinGW issue. * Change preprocessor file extensions to work with the installation system. * Support FreeBSD and other OSs that do not define _GNU_SOURCE but have _Unwind_Backtrace function. Thread: * Fix bug in boost::condition_variable on Windows @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.5 2017/09/01 10:02:01 abs Exp $ d12 1 a12 1 +# We want boost 1.65.1 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_65_1") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.65.1/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106501 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 65) d46 1 a46 1 + "we need 65" a49 13 @@@@ -272,10 +272,10 @@@@ ENDIF() MESSAGE(STATUS "BOOST_INCLUDE_DIR ${BOOST_INCLUDE_DIR}") # We have a limited set of patches/bugfixes here: -SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_59_0/patches") +SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_65_1/patches") # We have a limited set of source files here: -SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_59_0") +SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_65_1") # Bug in sqrt(NaN) on 32bit platforms IF(SIZEOF_VOIDP EQUAL 4) @ 1.5 log @Fix build for boost 1.65.0. Build fix so ride previous PKGREVISION bump @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.4 2017/04/30 05:10:32 adam Exp $ d12 1 a12 1 +# We want boost 1.65.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_65_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.65.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106500 d55 1 a55 1 +SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_65_0/patches") d59 1 a59 1 +SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_65_0") @ 1.4 log @Sync with boost 1.64.0 @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.3 2017/01/01 16:06:07 adam Exp $ d5 1 a5 1 --- cmake/boost.cmake.orig 2016-09-13 14:56:09.000000000 +0000 d12 1 a12 1 +# We want boost 1.64.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_64_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.64.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106400 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 64) d46 1 a46 1 + "we need 64" d55 1 a55 1 +SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_64_0/patches") d59 1 a59 1 +SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_64_0") @ 1.3 log @Revbump after boost update @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.2 2016/10/14 19:28:28 adam Exp $ d12 1 a12 1 +# We want boost 1.63.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_63_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.63.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106300 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 63) d46 1 a46 1 + "we need 63" d55 1 a55 1 +SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_63_0/patches") d59 1 a59 1 +SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_63_0") @ 1.2 log @Changes 5.7.16: Security Notes -------------- * Incompatible Change: For STANDALONE and WIN builds, the default secure_file_priv value has changed from the empty string to NULL. This is a secure-by-default setting because it disables import and export operations. To permit those operations, set secure_file_priv to the path name of the directory to use for those operations. * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1u. For a description of issues fixed in this version, see http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Functionality Added or Changed ------------------------------ * yaSSL was upgraded to version 2.4.2. This upgrade corrects issues with: Potential AES side channel leaks; DSA padding for unusual sizes; the SSL_CTX_load_verify_locations() OpenSSL compatibility function failing to handle long path directory names. @ text @d1 1 a1 1 $NetBSD: patch-cmake_boost.cmake,v 1.1 2016/09/16 06:49:11 adam Exp $ d12 1 a12 1 +# We want boost 1.62.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_62_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.62.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106200 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 62) d46 1 a46 1 + "we need 62" d55 1 a55 1 +SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_62_0/patches") d59 1 a59 1 +SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_62_0") @ 1.1 log @MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. @ text @d1 1 a1 1 $NetBSD$ d12 1 a12 1 +# We want boost 1.61.0 in order to build our boost/geometry code. d21 1 a21 1 +SET(BOOST_PACKAGE_NAME "boost_1_61_0") d25 1 a25 1 + "http://sourceforge.net/projects/boost/files/boost/1.61.0/${BOOST_TARBALL}" d34 1 a34 1 +# #define BOOST_VERSION 106100 d43 1 a43 1 +IF(NOT BOOST_MINOR_VERSION EQUAL 61) d46 1 a46 1 + "we need 61" d55 1 a55 1 +SET(BOOST_PATCHES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_61_0/patches") d59 1 a59 1 +SET(BOOST_SOURCES_DIR "${CMAKE_SOURCE_DIR}/include/boost_1_61_0") @