---
- branch: MAIN
  date: Sun Oct 30 12:53:55 UTC 2022
  files:
  - new: '1.44'
    old: '1.43'
    path: pkgsrc/databases/mysql57-client/Makefile
    pathrev: pkgsrc/databases/mysql57-client/Makefile@1.44
    type: modified
  - new: '1.39'
    old: '1.38'
    path: pkgsrc/databases/mysql57-client/Makefile.common
    pathrev: pkgsrc/databases/mysql57-client/Makefile.common@1.39
    type: modified
  - new: '1.26'
    old: '1.25'
    path: pkgsrc/databases/mysql57-client/PLIST
    pathrev: pkgsrc/databases/mysql57-client/PLIST@1.26
    type: modified
  - new: '1.50'
    old: '1.49'
    path: pkgsrc/databases/mysql57-client/distinfo
    pathrev: pkgsrc/databases/mysql57-client/distinfo@1.50
    type: modified
  - new: '1.45'
    old: '1.44'
    path: pkgsrc/databases/mysql57-server/Makefile
    pathrev: pkgsrc/databases/mysql57-server/Makefile@1.45
    type: modified
  - new: '1.25'
    old: '1.24'
    path: pkgsrc/databases/mysql57-server/PLIST
    pathrev: pkgsrc/databases/mysql57-server/PLIST@1.25
    type: modified
  id: 20221030T125355Z.2225095df9aaf4b64b3693889cce5d3fa7c2e5d0
  log: "mysql57: updated to 5.7.40\n\nChanges in MySQL 5.7.40\n\nFunctionality Added
    or Changed\n\nImportant Change: The linked OpenSSL library for MySQL Server has
    been updated to version 1.1.1q. Issues fixed in OpenSSL version 1.1.1q are described
    at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html.\n\nThe
    linked curl library for MySQL Server (Enterprise Edition) has been updated to
    version 7.84.0.\n\nMySQL Server窶å\x86± AES_ENCRYPT() and AES_DECRYPT() functions
    now support the use of a key derivation function (KDF) to create a cryptographically
    strong secret key from information such as a password or a passphrase that you
    pass to the function. The derived key is used to encrypt and decrypt the data,
    and it remains in the MySQL Server instance and is not accessible to users. Using
    a KDF is highly recommended, as it provides better security than specifying your
    own premade key or deriving it by a simpler method when you use the function.
    The functions support HKDF (available from OpenSSL 1.1.0), for which you can specify
    an optional salt and context-specific information to include in the keying material,
    and PBKDF2 (available from OpenSSL 1.0.2), for which you can specify an optional
    salt and set the number of iterations used to produce the key.\n\nBugs Fixed\n\nInnoDB:
    In debug builds, a descending b-tree scan raised a debug assertion failure.\n\nInnoDB:
    An index latch order violation in dict_table_x_lock_indexes() caused an assertion
    failure.\n\nInnoDB: A TRUNCATE TABLE operation failed to free an acquired mutex
    in specific cases.\n\nThe server did not always process nested views as expected.\n\nmysqlpump
    might not be given the correct permissions to use derived tables (tables that
    are generated by a query FROM clause), causing the dump process to stop if these
    were present. Derived tables are now handled separately and privileges are set
    for them.\n\nWhen using --log-timestamps=SYSTEM, ISO 8601 timestamps in log messages
    did not take account of daylight saving time.\n\nThe GRANT OPTION privilege was
    treated as related to database operations.\n\nChanges in MySQL 5.7.39\n\nCompilation
    Notes\n\nAdded macOS/ARM support.\n\nOn Windows, improved the generated INFO_BIN
    and INFO_SRC files.\n\nKeyring Notes\n\nThe keyring_aws plugin has been updated
    to use the latest AWS Encryption SDK for C (version 1.9.186).\n\nThe keyring_aws_region
    variable supports the additional AWS regions supported by the new SDK. Refer to
    the variable description for a list of supported AWS regions.\n\nPerformance Schema
    Notes\n\nThe SHOW PROCESSLIST statement provides process information by collecting
    thread data from all active threads. However, because the implementation iterates
    across active threads from within the thread manager while holding a global mutex,
    it has negative performance consequences, particularly on busy systems.\n\nAn
    alternative SHOW PROCESSLIST implementation is now available based on the new
    Performance Schema processlist table. This implementation queries active thread
    data from the Performance Schema rather than the thread manager and does not require
    a mutex:\n\nTo enable the alternative implementation, enable the performance_schema_show_processlist
    system variable.\n\nNote\nThe processlist table is automatically created in the
    Performance Schema for new installations of MySQL 5.7.39, or higher, and upgrades
    to MySQL 5.7.39, or higher.\n\nThe alternative implementation of SHOW PROCESSLIST
    also applies to the mysqladmin processlist command.\n\nThe alternative implementation
    does not apply to the INFORMATION_SCHEMA PROCESSLIST table or the COM_PROCESS_INFO
    command of the MySQL client/server protocol.\n\nTo ensure that the default and
    alternative implementations yield the same information, certain configuration
    requirements must be met; see The processlist Table.\n\nFunctionality Added or
    Changed\n\nImportant Change: The linked curl library for MySQL Server (Enterprise
    Edition) has been updated to version 7.83.1.\n\nImportant Change: The linked OpenSSL
    library for MySQL Server has been updated to version 1.1.1o. Issues fixed in OpenSSL
    version 1.1.1o are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html.\n\nThe
    myisam_repair_threads system variable and myisamchk --parallel-recover option
    were removed.\n\nBugs Fixed\n\nInnoDB: A 4GB tablespace file size limit on Windows
    32-bit systems has been removed. The limit was due to an incorrect calculation
    performed while extending the tablespace.\n\nReplication: The write sets extracted
    by MySQL Replication from transactions when the transaction_write_set_extraction
    system variable is enabled (which is the default) are extracted from primary keys,
    unique keys, and foreign keys. They are used to detect dependencies and conflicts
    between transactions. Previously, write sets involving multi-column foreign keys
    were incorrectly identifying each column as a separate foreign key. The issue
    has now been fixed and foreign key write sets include all referenced key columns.\n\nReplication:
    When the --replicate-same-server-id option was used to make the replica not skip
    events that have its own server ID, if the log file was rotated, replication stopped
    with an error. The log rotation event now checks and applies the current value
    of the option.\n\nUnder certain circumstances TRUNCATE performance_schema.accounts
    caused duplicated counts in global_status.\n\nThis occurred only if the following
    was true:\n\nIf show_compatibility_56 is set to 0, aggregating status variables
    by accounts, users and hosts.\n\nIf some hosts were not instrumented. For example,
    if performance_schema_hosts_size was set to a low value.\n\nOur thanks to Yuxiang
    Jiang and the Tencent team for the contribution.\n\nUpgraded the bundled zlib
    library to zlib 1.2.12. Also made zlib 1.2.12 the minimum zlib version supported,
    and removed WITH_ZLIB from the WITH_SYSTEM_LIBS CMake option.\n\nIf an incorrect
    value was set for the binlog_checksum system variable during a session, a COM_BINLOG_DUMP
    command made in the same session to request a binary log stream from a source
    failed. The server now validates the specified checksum value before starting
    the checksum algorithm setup process.\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/databases'
  unixtime: '1667134435'
  user: adam