./databases/mysql57-server, MySQL 5, a free SQL database (server)

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 5.7.21nb1, Package name: mysql-server-5.7.21nb1, Maintainer: pkgsrc-users

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

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.

The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL).

This package contains the MySQL server programs and libraries including
embedded server (by PKG_OPTION).

MESSAGE.sphinx [+/-]

Required to run:
[lang/perl5] [devel/boost-libs] [devel/editline] [archivers/lz4] [databases/mysql57-client]

Required to build:
[devel/boost-headers] [pkgtools/cwrappers]

Package options: embedded-server

Master sites: (Expand)

SHA1: 4ba0af75db7d5b33c30f20bdda2d059abc355a47
RMD160: 7a70e573e4d9075bc62768f65509fe1c0e024a60
Filesize: 50608.039 KB

Version history: (Expand)

CVS history: (Expand)

   2018-02-25 02:15:22 by Mark Davies | Files touched by this commit (7)
Log message:
mysql57-{client,server}: support openssl 1.1
   2018-02-20 13:57:32 by Thomas Klausner | Files touched by this commit (1)
Log message:
mysql57-server: remove reference to non-existing file
   2018-01-16 17:29:42 by Adam Ciarcinski | Files touched by this commit (10) | Package updated
Log message:
mysql57: updated to 5.7.21

MySQL 5.7.21

Audit Log Notes
* MySQL Enterprise Audit now supports compression and encryption of audit log \ 
files. Encryption is based on a user-defined password. To use this feature, the \ 
MySQL keyring must be enabled because audit logging uses it for password \ 
storage. MySQL Enterprise Audit also now supports logging in JSON format, in \ 
addition to the existing XML formats. For JSON format, functions are available \ 
that provide runtime log reading capabilities. For additional information, see \ 
MySQL Enterprise Audit.

Configuration Notes
* For RHEL, SLES, and Fedora RPMs, the default plugin directory for debug builds \ 
has been changed from /usr/lib64/mysql/plugin to /usr/lib64/mysql/plugin/debug.
* The installation scripts for MySQL Enterprise Audit and MySQL Enterprise \ 
Firewall now create their associated tables in the mysql system database as \ 
InnoDB rather than MyISAM tables.
* The hardcoded memory page size of 8KB for the memory-mapped transaction \ 
coordinator was too small for platforms such as ARM64 and PowerPC where the page \ 
size is much larger. The server now invokes a system call to get the page size \ 
of the current platform rather than using a hardcoded value. A consequence for \ 
the --log-tc-size option is that the minimum and default values are now 6 times \ 
the page size. Also, the value must be a multiple of the page size. Thanks to \ 
Alexey Kopytov for the patch.

Performance Schema Notes
* The Performance Schema setup_timers table is now deprecated, to be removed in \ 
MySQL 8.0, as is the TICK row in the performance_timers table.

Pluggable Authentication
* For the LDAP authentication plugins, handling of the group search attribute \ 
indicated by the authentication_ldap_sasl_group_search_attr and \ 
authentication_ldap_simple_group_search_attr system variables is more flexible. \ 
If the group search attribute is isMemberOf, LDAP authentication directly \ 
retrieves the user attribute isMemberOf value and assign it as group \ 
information. If the group search attribute is not isMemberOf, LDAP \ 
authentication searches for all groups where the user is a member. (The latter \ 
is the default behavior.) This behavior is based on how LDAP group information \ 
can be stored two ways: 1) A group entry can have an attribute named memberUid \ 
or member with a value that is a user name; 2) A user entry can have an \ 
attribute named isMemberOf with values that are group names.
* The LDAP authentication plugins now permit the authentication string that \ 
provides user DN information to begin with a + character. In the absence of this \ 
character, the authentication string value is treated as is without \ 
modification, as it has been previously. If the authentication string begins \ 
with +, the plugin constructs the full user DN value from the account user name \ 
as the cn attribute value, together with the authentication string (with the + \ 
removed). The authentication string is stored as given in the mysql.user system \ 
table, with the full user DN constructed on the fly before authentication.
* For the LDAP authentication plugins, the group search attribute was fixed and \ 
not configurable. Two new system variables now enable using custom group \ 
filters: authentication_ldap_sasl_group_search_filter and \ 

Security Notes
* Incompatible Change: Passwords are now restricted to a maximum of 256 \ 
characters for the sha256_password authentication plugin, and for the PASSWORD() \ 
function when old_passwords=2. Also, the number of password hashing rounds is \ 
capped to limit CPU time used.
* The linked OpenSSL library for the MySQL Commercial Server has been updated to \ 
version 1.0.2n. Issues fixed in the new OpenSSL version are described at \ 
* This change does not affect the Oracle-produced MySQL Community build of MySQL \ 
Server, which uses the yaSSL library instead.
* MySQL now supports key migration between underlying keyring keystores. This \ 
enables DBAs to switch a MySQL installation from one keyring plugin to another. \ 
See Migrating Keys Between Keyring Keystores.
* MySQL Enterprise Edition now includes a keyring plugin, \ 
keyring_encrypted_file, that is similar to the keyring_file plugin in its use of \ 
a local data file for key storage, but that also encrypts the file based on a \ 
user-defined password. See Using the keyring_encrypted_file Keyring Plugin.
   2018-01-01 22:18:57 by Adam Ciarcinski | Files touched by this commit (629) | Package updated
Log message:
Revbump after boost update
   2017-10-22 22:20:57 by Adam Ciarcinski | Files touched by this commit (7) | Package updated
Log message:
mysql57: update to 5.7.20

Changes in MySQL 5.7.20:

Audit Log Notes

Event-matching filter rules for the audit_log plugin now support an abort \ 
element, which can be used to prevent qualifying events from executing. For more \ 
information, see Audit Log Filtering. This capability can be used, for example, \ 
to augment the capabilities of MySQL Enterprise Firewall, which blocks SQL \ 
statements on a per-user basis, by writing audit filtering rules that match \ 
statements and block them based on characteristics of the statements themselves.

Deprecation and Removal Notes

Previously, the --transaction-isolation and --transaction-read-only server \ 
startup options corresponded to the tx_isolation and tx_read_only system \ 
variables. For better name correspondence between startup option and system \ 
variable names, transaction_isolation and transaction_read_only have been \ 
created as aliases for tx_isolation and tx_read_only. The tx_isolation and \ 
tx_read_only variables are now deprecated and will be removed in MySQL 8.0. \ 
Applications should be adjusted to use transaction_isolation and \ 
transaction_read_only instead.

The query cache is now deprecated and is removed in MySQL 8.0. Deprecation \ 
includes these items:
* The SQL_CACHE and SQL_NO_CACHE SELECT modifiers.
* These system variables: have_query_cache, ndb_cache_check_time, \ 
query_cache_limit, query_cache_min_res_unit, query_cache_size, query_cache_type, \ 
* These status variables: Qcache_free_blocks, Qcache_free_memory, Qcache_hits, \ 
Qcache_inserts, Qcache_lowmem_prunes, Qcache_not_cached, \ 
Qcache_queries_in_cache, Qcache_total_blocks.

The mysql client by default strips comments in statements sent to the server, \ 
and this behavior is controlled using --skip-comments (strip comments), and \ 
--comments (preserve comments).
Comment stripping is now deprecated. This feature and the options to control it \ 
will be removed in a future MySQL release.

These syntax constructs for table and column references are now deprecated and \ 
will be removed in a future version of MySQL. Instances of these constructs \ 
should be changed to remove the leading period.
* .col_name
* .tbl_name
* .tbl_name.col_name

Security Notes

Certificates automatically generated by mysqld and mysql_ssl_rsa_setup now use \ 
X509 v3 rather than v1.
The keyring_okv plugin now supports password-protecting the key file used for \ 
secure connections. See Using the keyring_okv KMIP Plugin.

Bugs Fixed
   2017-09-13 19:34:41 by Adam Ciarcinski | Files touched by this commit (8) | Package updated
Log message:
boost: update to 1.65.1

Fixes in 1.65.1
* Version macro changes for CUDA.
* Update last known MSVC version.
* MSVC 14.11 supports structured bindings.

* Return a continuation from functions executed by resume_with.

* Return a continuation from functions executed by resume_with.

Smart Pointers:
* Fix Visual C++ version checks.
* Fix compilation for NVCC with host compiler clang.

* 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.

* Fix bug in boost::condition_variable on Windows
   2017-08-24 22:03:43 by Adam Ciarcinski | Files touched by this commit (621) | Package updated
Log message:
Revbump for boost update
   2017-07-20 18:41:10 by Adam Ciarcinski | Files touched by this commit (8) | Package updated
Log message:
Security Notes
* Security Fix: The linked OpenSSL library for the MySQL Commercial Server has \ 
been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are \ 
described at 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.

Platform-Specific Notes
* Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 \ 
using glibc 2.12. Systems that use the build need to have glibc 2.12 or later \ 
installed on them.

Functionality Added or Changed
* For Windows, MSI installer packages now include a check for the required \ 
Visual Studio redistributable package, and produce a message asking the user to \ 
install it if it is missing.
* The mysql client now supports a --binary-as-hex option that causes display of \ 
binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden \ 
for the patch.
* mysqlaccess now looks for its configuration file only in the SYSCONFDIR \ 
directory and /etc.

Bugs Fixed
* InnoDB: The server allocated memory unnecessarily for an operation that \ 
rebuilt the table.
* InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) \ 
operation sometimes returned 0. Partitioning code incorrectly performed a memcpy \ 
instead of a column copy of columns read by the index, causing the wrong records \ 
to be copied.
* Replication: A USE statement that followed a SET GTID_NEXT statement sometimes \ 
had no effect.
* Replication: If the binary log on a master server was rotated and a full disk \ 
condition occurred on the partition where the binary log file was being stored, \ 
the server could stop unexpectedly. The fix adds a check for the existence of \ 
the binary log when the dump thread switches to next binary log file. If the \ 
binary log is disabled, all binary logs up to the current active log are \ 
transmitted to slave and an error is returned to the receiver thread.
* Replication: If a relay log index file named relay log files that did not \ 
exist, RESET SLAVE ALL sometimes did not fully clean up properly.
* Replication: mysqlbinlog, if invoked with the --raw option, does not flush the \ 
output file until the process terminates. But if also invoked with the \ 
--stop-never option, the process never terminates, thus nothing is ever written \ 
to the output file. Now the output is flushed after each event.
* Replication: A memory leak in mysqlbinlog was fixed. The leak happened when \ 
processing fake rotate events, or when using --raw and the destination log file \ 
could not be created. The leak only occurred when processing events from a \ 
remote server. Thanks to Laurynas Biveinis for his contribution to fixing this \ 
* Replication: Multi-threaded slaves could not be configured with small queue \ 
sizes using slave_pending_jobs_size_max if they ever needed to process \ 
transactions larger than that size. Any packet larger than \ 
slave_pending_jobs_size_max was rejected with the error \ 
ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than \ 
the limit set by slave_max_allowed_packet.
* With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a \ 
hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is \ 
less than slave_max_allowed_packet, the transaction is held until all the slave \ 
workers have empty queues, and then processed. All subsequent transactions are \ 
held until the large transaction has been completed. The queue size for slave \ 
workers can therefore be limited while still allowing occasional larger \ 
* mysqldump could write database names in USE statements incorrectly.
* If the mysql_stmt_close() C API function was called, it freed memory that \ 
later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or \ 
mysql_stmt_sqlstate() was called. To obtain error information after a call to \ 
mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() \ 
* Queries could be cached incorrectly, leading to incorrect query results, under \ 
these circumstances: InnoDB table; rows are being inserted but have not yet been \ 
committed; a query uses the table as a base table in a derived table; the \ 
optimizer chooses to materialize the derived table.
* Man pages for a few utilities were missing from Debian/Ubuntu packages.
* The field-t unit test failed to run with AddressSanitizer enabled. Thanks to \ 
Laurynas Biveinis for the patch.
* Debian client packages were missing information about conflicts with native \ 
* The Perl path in #! lines at the beginning of Perl scripts has been adjusted \ 
to /usr/local/bin/perl for FreeBSD 11.
* The server exited abnormally attempting to access invalid memory.
* A race condition could occur for CREATE TABLE statements with DATA DIRECTORY \ 
* MySQL compilation in different directories produced different builds to \ 
leakage of absolute paths into debug information and __FILE__.
* mysqld_failed to start the server if the --datadir option was specified with a \ 
relative path name.
* With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users \ 
was permitted under certain conditions.
*Certain stored functions, if used in a query WHERE clause, could be handled \ 
using Index Condition Pushdown (which should not happen), resulting in a server \ 
* On x86 machines, the uint3korr() macro read 4 bytes of data instead of the \ 
intended 3 bytes.
* An assertion was raised during a fetch operation by the memcached plugin.
* Queries that contained UNION in a subquery and GROUP BY could return incorrect \ 
* LOAD XML INFILE performance became noticeably slower when the XML file being \ 
read contained a great many spaces, such as those introduced by indenting or \ 
pretty-printing. Now all leading whitespace is trimmed from each such value \ 
before reading it into memory.