1. 28 Jun, 2007 2 commits
  2. 27 Jun, 2007 1 commit
    • unknown's avatar
      BUG#29207 - archive table reported as corrupt by check table (P1) · 09992cba
      unknown authored
      CHECK TABLE against ARCHIVE table may falsely report table corruption,
      or cause server crash.
      
      Fixed by using proper buffer for CHECK TABLE.
      
      Affects both 5.0 and 5.1.
      
      
      mysql-test/r/archive.result:
        A test case for BUG#28916.
      mysql-test/t/archive.test:
        A test case for BUG#28916.
      sql/ha_archive.cc:
        We call Field::get_length() from get_row(). Field::get_length() assumes
        that the row was read into table->record[0] buffer, which is not the
        case when we check a table. As a result we get wrongly initialized
        blob length.
        
        Use table->record[0] as record buffer for check table instead.
      09992cba
  3. 25 Jun, 2007 1 commit
    • unknown's avatar
      BUG#28026 - Falcon: crash if partitions and select for update · f2e443ca
      unknown authored
      Assertion failure may happen with falcon + partition + select for
      update. This may affect other engines as well.
      
      Though assertion failure is fixed with this patch, falcon still
      deadlocks when running falcon_bug_28026.test.
      
      
      sql/ha_partition.cc:
        In case rnd_next fails, we must call ha_rnd_end. This is done
        conditionally (NO_CURRENT_PART_ID != m_part_spec.start_part)
        in ha_partition::ha_rnd_end. Thus we may not reset
        m_part_spec.start_part in case rnd is not ended.
      f2e443ca
  4. 24 Jun, 2007 2 commits
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG15787/mysql-5.0-engines · 376ff548
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG15787/mysql-5.1-engines
      
      
      storage/archive/ha_archive.cc:
        Use local.
      376ff548
    • unknown's avatar
      BUG#15787 - MySQL crashes when archive table exceeds 2GB · 0f01d4a9
      unknown authored
      Max compressed file size was calculated incorretly causing server
      crash on INSERT.
      
      With this patch we use proper max file size provided by zlib.
      
      Affects 5.0 only.
      
      
      sql/ha_archive.cc:
        When calculating max compressed file size, use the real offset size
        that is provided by zlib, instead of sizeof(z_off_t), which may be
        different from actual offset size.
        
        When we're about to write and the data file is almost full flush gzio
        buffer to get accurate real file size.
      mysql-test/r/archive-big.result:
        New BitKeeper file ``mysql-test/r/archive-big.result''
      mysql-test/t/archive-big.test:
        New BitKeeper file ``mysql-test/t/archive-big.test''
      0f01d4a9
  5. 22 Jun, 2007 1 commit
  6. 19 Jun, 2007 1 commit
    • unknown's avatar
      mtr_report.pl: · f1a732ef
      unknown authored
        Ignore warning about file name
        having question marks.
      
      
      mysql-test/lib/mtr_report.pl:
        Ignore warning about file name
        having question marks.
      f1a732ef
  7. 18 Jun, 2007 6 commits
  8. 17 Jun, 2007 20 commits
  9. 16 Jun, 2007 6 commits