---
- branch: MAIN
  date: Sun Apr  8 18:30:27 UTC 2012
  files:
  - new: '1.16'
    old: '1.15'
    path: pkgsrc/databases/mysql55-client/Makefile.common
    pathrev: pkgsrc/databases/mysql55-client/Makefile.common@1.16
    type: modified
  - new: '1.13'
    old: '1.12'
    path: pkgsrc/databases/mysql55-client/distinfo
    pathrev: pkgsrc/databases/mysql55-client/distinfo@1.13
    type: modified
  - new: '1.14'
    old: '1.13'
    path: pkgsrc/databases/mysql55-server/PLIST
    pathrev: pkgsrc/databases/mysql55-server/PLIST@1.14
    type: modified
  id: 20120408T183027Z.39de08d70869db4dc815b8e556c6bc5876c83f35
  log: |
    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: pkgsrc
  subject: 'CVS commit: pkgsrc/databases'
  unixtime: '1333909827'
  user: adam