pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

CVS commit: pkgsrc/databases

Module Name:    pkgsrc
Committed By:   adam
Date:           Thu Jan 12 16:33:49 UTC 2012

Modified Files:
        pkgsrc/databases/mysql55-client: Makefile.common distinfo
        pkgsrc/databases/mysql55-server: PLIST

Log Message:
Changes 5.5.20:
* A new server option, --slow-start-timeout, controls the Windows service
  control manager's service start timeout. The value is the maximum number of
  milliseconds that the service control manager waits before trying to kill the
  MySQL service during startup. The default value is 15000 (15 seconds). If the
  MySQL service takes too long to start, you may need to increase this value.
  A value of 0 means there is no timeout.

Bugs Fixed:
* Important Change: Replication: Setting an empty user in a CHANGE MASTER TO
  statement caused an invalid internal result and is no longer permitted. 
Trying  to use MASTER_USER='' or setting MASTER_PASSWORD while leaving 
  unset causes the statement to fail with an error.
* Important Change: Replication: Moving the binary log file, relay log file, or
  both files to a new location, then restarting the server with a new value for
  --log-bin, --relay-log, or both, caused the server to abort on start. This
  was because the entries in the index file overrode the new location. In
  addition, paths were calculated relative to datadir (rather than to the
  --log-bin or --relay-log values).
* InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, 
  with innodb_page_size set to a value other than 16384, now the earlier MySQL
  version reports that the page size is incompatible with the older version,
  rather than crashing or displaying a “corruption” error.
* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for
  InnoDB tables from concurrent threads could cause a deadlock, particularly
  with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks
  caused by the same row being accessed by more than one transaction. Deadlocks
  could still occur when multiple rows are inserted and updated simultaneously
  by different transactions in inconsistent order; those types of deadlocks
  require the standard error handling on the application side, of re-trying the
* An incorrect InnoDB assertion could cause the server to halt. This issue only
  affected debug builds. The assertion referenced the source file btr0pcur.ic
  and the variable cursor->pos_state.
* Locale information for FORMAT() function instances was lost in view
* The handle_segfault() signal-handler code in mysqld could itself crash due to
  calling unsafe functions.
* Enabling myisam_use_mmap could cause the server to crash.
* Concurrent access to ARCHIVE tables could cause corruption.

To generate a diff of this commit:
cvs rdiff -u -r1.12 -r1.13 pkgsrc/databases/mysql55-client/Makefile.common
cvs rdiff -u -r1.10 -r1.11 pkgsrc/databases/mysql55-client/distinfo
cvs rdiff -u -r1.10 -r1.11 pkgsrc/databases/mysql55-server/PLIST

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Home | Main Index | Thread Index | Old Index