./databases/mysql56-client, MySQL 5, a free SQL database (client)

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

Branch: CURRENT, Version: 5.6.44nb1, Package name: mysql-client-5.6.44nb1, 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 client programs and libraries.

Required to run:
[lang/perl5] [devel/editline]

Required to build:

Package options: embedded-server, ssl

Master sites: (Expand)

SHA1: 7bc331b735c480fc48427e7c8986a2bb82538d6c
RMD160: 6a6c0a18503e5f6b758e76c76d612a4ada3a8296
Filesize: 31769.05 KB

Version history: (Expand)

CVS history: (Expand)

   2019-06-05 11:35:18 by Jonathan Perkin | Files touched by this commit (1)
Log message:
mysql56-client: Disable epoll in bundled libevent too.
   2019-04-30 19:20:23 by David Brownlee | Files touched by this commit (8) | Package updated
Log message:
   2019-04-30 16:09:52 by David Brownlee | Files touched by this commit (3)
Log message:
Add USE_GCC_RUNTIME to mysql{51,55,56}
   2019-04-25 10:53:43 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
mysql56: updated to 5.6.44

Unknown changes
   2019-02-05 21:18:43 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
mysql56-client: fix some pkglint issues
   2019-02-05 21:14:56 by Adam Ciarcinski | Files touched by this commit (1)
Log message:
Fix pkgbase
   2019-02-05 21:06:06 by Adam Ciarcinski | Files touched by this commit (7) | Package updated
Log message:
mysql56-{client,server}: updated to 5.6.43

Changes in MySQL 5.6.43:

Functionality Added or Changed

Microsoft Windows: The access control granted to clients on the named pipe \ 
created by the MySQL server now is set to the minimum necessary for successful \ 
communication on Windows. Newer MySQL client software can open named pipe \ 
connections without any additional configuration. If older client software \ 
cannot be upgraded immediately, the new named_pipe_full_access_group server \ 
system variable can be used to give a Windows group the necessary permissions to \ 
open a named pipe connection. Membership in the full-access group should be \ 
restricted and temporary.

Bugs Fixed

Replication: A patch to correct the handling of quotes for identifiers in \ 
ROLLBACK TO SAVEPOINT statements in the binary log was not correctly applied to \ 
subsequent MySQL versions.

Replication: In some circumstances, the CHANGE MASTER TO statement could not be \ 
used on a replication slave if the master info log had been changed from a table \ 
(master_info_repository=TABLE) into a file (master_info_repository=FILE).

Replication: The value returned by a SHOW SLAVE STATUS statement for the total \ 
combined size of all existing relay log files (Relay_Log_Space) could become \ 
much larger than the actual disk space used by the relay log files. The I/O \ 
thread did not lock the variable while it updated the value, so the SQL thread \ 
could automatically delete a relay log file and write a reduced value before the \ 
I/O thread finished updating the value. The I/O thread then wrote its original \ 
size calculation, ignoring the SQL thread's update and so adding back the space \ 
for the deleted file. The Relay_Log_Space value is now locked during updates to \ 
prevent concurrent updates and ensure an accurate calculation.

Replication: If the relay log index file was temporarily locked for viewing by a \ 
backup process for a replication slave, and MySQL Server also attempted to \ 
access the file at that time for rename or delete operations, the backup \ 
completed with warnings, but MySQL Server experienced an unexpected halt. MySQL \ 
Server now retries the file access operation a number of times in case this or a \ 
similar scenario is the explanation and the file becomes available again before \ 

The server permitted creation of databases with the same name as redo log files, \ 
which could result in unexpected server behavior. Such names are no longer \ 
permitted as database names.

When a subquery contained a UNION, the count of the number of subquery columns \ 
was calculated incorrectly.

Comparing log file names as strings using the memcmp() function resulted in \ 
uninitialized memory read errors. The comparison now uses the strncmp() \ 
function. Thanks to Zsolt Parragi and Laurynas Biveinis for their contributions.

The transformation of IN subquery predicates into semijoins was not handled \ 
correctly for a very large number of tables.

Executing a prepared statement to do a multiple-row insert with large number of \ 
placeholders consumed excessive memory and could execute slowly.

The parser accepted invalid SET statement syntax in trigger definitions that \ 
could result in a server exit.

MyISAM index corruption could occur for bulk-insert and table-repair operations \ 
that involve the repair-by-sorting algorithm and many (more than 450 million) \ 

A query employing a dynamic range and an index merge could use more memory than \ 
   2019-01-20 19:04:49 by Maya Rashish | Files touched by this commit (5)
Log message:
mysql56-client: change the default configuration to avoid information
disclosure to a malicious server.

Backport of upstream commit:
https://github.com/mysql/mysql-server/c … d3bd1777be

Exploit method described here:
https://gwillem.gitlab.io/2019/01/17/ad … erability/