Log message:
Pullup ticket #3787 - requested by taca
databases/mysql55-client: security update
databases/mysql55-server: security update

Revisions pulled up:
- databases/mysql55-client/Makefile.common                      1.16-1.18
- databases/mysql55-client/distinfo                             1.13-1.15
- databases/mysql55-server/PLIST                                1.14-1.16

---
   Module Name:	pkgsrc
   Committed By:	adam
   Date:		Sun Apr  8 18:30:27 UTC 2012

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

   Log message:
   Changes 5.5.22:
   * InnoDB Storage Engine: A deprecation warning is now issued when
     --ignore-builtin-innodb is used.
   * yaSSL was upgraded from version 1.7.2 to 2.2.0.
   * Security Fix: Bug 13510739 and Bug 63775 were fixed.
   * Important Change: InnoDB Storage Engine: When a row grew in size due to an
     UPDATE operation, other (non-updated) columns could be moved to off-page
     storage so that information about the row still fit within the constraints of
     the InnoDB page size. The pointer to the new allocated off-page data was not
     set up until the pages were allocated and written, potentially leading to
     lost data if the system crashed while the column was being moved out of the
     page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or
     ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with
     the innodb_file_per_table setting enabled, because page allocation operations
     are more common as the .ibd tablespace files are extended. Still, the problem
     could occur with any combination of InnoDB version, file format, and row
     format.
   * InnoDB Storage Engine: An erroneous assertion could occur, in debug builds
     only, when creating an index on a column containing zero-length values (that
     is, '').
   * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN
     could stall, eventually timing out with an Error 1005: Can't create table
     message referring to fil_rename_tablespace.
   * InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy
     MySQL server to halt with an assertion error:
   More...

---
   Module Name:	pkgsrc
   Committed By:	adam
   Date:		Sat Apr 14 12:10:05 UTC 2012

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

   Log message:
   Changes 5.5.23:
   Bugs Fixed
   * Security Fix: Bug 59533 was fixed.
   * Performance: Partitioning: InnoDB Storage Engine: The statistics used by the
     optimizer for queries against partitioned InnoDB tables were based only on the
     first partition of each such table, leading to use of the wrong execution
     plan.
   * References: This bug was introduced by Bug 11756867.
   * Performance: InnoDB Storage Engine: Improved the performance of the DROP TABLE
     statement for InnoDB tables, especially on systems with a large buffer pool.
     The fix speeds up the processing for freeing entries in the adaptive hash
     index.
   * InnoDB Storage Engine: Deleting a huge amount of data from InnoDB tables
     within a short time could cause the purge operation that flushes data from the
     buffer pool to stall. If this issue occurs, restart the server to work around
     it. This issue is only likely to occur on 32-bit platforms.
   * InnoDB Storage Engine: If the server crashed during a TRUNCATE TABLE or CREATE
     INDEX statement for an InnoDB table, or a DROP DATABASE statement for
     a database containing InnoDB tables, an index could be corrupted, causing an
     error message when accessing the table after restart:
     InnoDB: Error: trying to load index index_name for table table_name
     InnoDB: but the index tree has been freed!
     In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in
     InnoDB storage engine.
   * InnoDB Storage Engine: When data was removed from an InnoDB table, newly
     inserted data might not reuse the freed disk blocks, leading to an unexpected
     size increase for the system tablespace or .ibd file (depending on the
     setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file
     in some cases but not others. The freed disk blocks would eventually be
     reused as additional data was inserted.
   More...

---
   Module Name:	pkgsrc
   Committed By:	taca
   Date:		Sun May 13 13:05:33 UTC 2012

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

   Log message:
   Update mysql55-{client,server} to 5.55.24.

   Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html):

   Functionality Added or Changed

       * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now
         marked as unsafe for statement-based replication if the target table has
         more than one primary or unique key. For more information, see Section
         16.1.2.3, "Determination of Safe and Unsafe Statements in Binary
         Logging".

   Bugs Fixed

       * Security Fix: Bug #64884 was fixed.

       * InnoDB: Replication: When binary log statements were replayed on the
         slave, the Com_insert, Com_update, and Com_delete counters were
         incremented by BEGIN statements initiating transactions affecting InnoDB
         tables but not by COMMIT statements ending such transactions. This
         affected these statements whether they were replicated or they were run
         using mysqlbinlog. (Bug #12662190)

       * If the --bind-address option was given a host name value and the host
         name resolved to more than one IP address, the server failed to
         start. For example, with --bind-address=localhost, if localhost resolved
         to both 127.0.0.1 and ::1, startup failed. Now the server prefers the
         IPv4 address in such cases. (Bug #61713, Bug #12762885)

       * mysql_store_result() and mysql_use_result() are not for use with
         prepared statements and are not intended to be called following
         mysql_stmt_execute(), but failed to return an error when invoked that
         way in libmysqld. (Bug #62136, Bug #13738989)

         References: See also Bug #47485.

       * On Windows, mysqlslap crashed for attempts to connect using shared
         memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)