• unknown's avatar
    Applied innodb-5.1-ss1404 snapshot · 878fe479
    unknown authored
    Fixes:
    
    - Bug #26662: mysqld assertion when creating temporary (InnoDB) table on a tmpfs filesystem
      Fix by not open(2)ing with O_DIRECT but rather calling fcntl(2) to set
      this flag immediately after open(2)ing. This way an error caused by
      O_DIRECT not being supported can easily be ignored.
    - Bug #23313: AUTO_INCREMENT=# not reported back for InnoDB tables
    - Bug #21404: AUTO_INCREMENT value reset when Adding FKEY (or ALTER?)
      Report the current value of the AUTO_INCREMENT counter to MySQL.
    
    
    mysql-test/r/innodb.result:
      Applied innodb-5.1-ss1404 snapshot
      
      Revision r1404:
      Report the current value of the AUTO_INCREMENT counter to MySQL.
      (Bug #23313, Bug #21404)
      
      ha_innobase::update_create_info(): New function, to report
      the auto_increment_value.
    mysql-test/t/innodb.test:
      Applied innodb-5.1-ss1404 snapshot
      
      Revision r1404:
      Report the current value of the AUTO_INCREMENT counter to MySQL.
      (Bug #23313, Bug #21404)
      
      ha_innobase::update_create_info(): New function, to report
      the auto_increment_value.
    storage/innobase/handler/ha_innodb.cc:
      Applied innodb-5.1-ss1404 snapshot
      
      Revision r1404:
      Report the current value of the AUTO_INCREMENT counter to MySQL.
      (Bug #23313, Bug #21404)
      
      ha_innobase::update_create_info(): New function, to report
      the auto_increment_value.
    storage/innobase/handler/ha_innodb.h:
      Applied innodb-5.1-ss1404 snapshot
      
      Revision r1404:
      Report the current value of the AUTO_INCREMENT counter to MySQL.
      (Bug #23313, Bug #21404)
      
      ha_innobase::update_create_info(): New function, to report
      the auto_increment_value.
    storage/innobase/os/os0file.c:
      Applied innodb-5.1-ss1404 snapshot
      
      Revision r1395:
      * Fix Bug#26662 by not open(2)ing with O_DIRECT but rather calling fcntl(2)
      to set this flag immediately after open(2)ing. This way an error caused by
      O_DIRECT not being supported can easily be ignored.
      
      * Add support for skipping the OS caching on Solaris by calling directio()
      instead of fcntl().
      
      Approved by:	Heikki
      
      
      
      Revision r1391:
      Merge the bodies of os_file_handle_error() and os_file_handle_error_no_exit()
      into a generic function which is called from both os_file_handle_error() and
      os_file_handle_error_no_exit()
      
      Approved by:	Marko
    storage/innobase/plug.in:
      Applied innodb-5.1-ss1404 snapshot
      
      Revision r1395:
      * Fix Bug#26662 by not open(2)ing with O_DIRECT but rather calling fcntl(2)
      to set this flag immediately after open(2)ing. This way an error caused by
      O_DIRECT not being supported can easily be ignored.
      
      * Add support for skipping the OS caching on Solaris by calling directio()
      instead of fcntl().
      
      Approved by:	Heikki
    878fe479
innodb.result 93.3 KB