An error occurred fetching the project authors.
  1. 19 Nov, 2007 1 commit
    • holyfoot/hf@mysql.com/hfmain.(none)'s avatar
      Bug #30284 spatial key corruption. · 140dd4f3
      holyfoot/hf@mysql.com/hfmain.(none) authored
      SPATIAL key is fine actually, but the chk_key() function
      mistakenly returns error. It tries to compare checksums
      of btree and SPATIAL keys while the checksum for the SPATIAL isn't
      calculated (always 0). Same thing with FULLTEXT keys is handled
      using full_text_keys counter, so fixed by counting both
      SPATIAL and FULLTEXT keys in that counter.
      140dd4f3
  2. 06 Nov, 2007 1 commit
    • istruewing@stella.local's avatar
      Bug#4692 - DISABLE/ENABLE KEYS waste a space · 30b409bd
      istruewing@stella.local authored
      Disabling and enabling indexes on a non-empty table grows the
      index file.
      
      Disabling indexes just sets a flag per non-unique index and does not
      free the index blocks of the affected indexes. Re-enabling indexes
      creates new indexes with new blocks. The old blocks remain unused
      in the index file.
      
      Fixed by dropping and re-creating all indexes if non-empty disabled
      indexes exist when enabling indexes. Dropping all indexes resets
      the internal end-of-file marker to the end of the index file header.
      It also clears the root block pointers of every index and clears the
      deleted blocks chains. This way all blocks are declared as free.
      30b409bd
  3. 16 May, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#25712 - insert delayed and check table run together report crashed · 3ea2ee35
      svoj@mysql.com/april.(none) authored
                  tables
      
      In case system doesn't have native pread/pwrite calls (e.g. Windows)
      and there is CHECK TABLE runs concurrently with another statement that
      reads from a table, the table may be reported as crashed.
      
      This is fixed by locking file descriptor when my_seek is executed on
      MyISAM index file and emulated pread/pwrite may be executed concurrently.
      
      Affects MyISAM tables on platforms that do not have native
      pread/pwrite calls (e.g. Windows).
      
      No deterministic test case for this bug.
      3ea2ee35
  4. 31 Dec, 2006 1 commit
    • kent@mysql.com/kent-amd64.(none)'s avatar
      my_strtoll10-x86.s: · 6523aca7
      kent@mysql.com/kent-amd64.(none) authored
        Corrected spelling in copyright text
      Makefile.am:
        Don't update the files from BitKeeper
      Many files:
        Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header
        Adjusted year(s) in copyright header 
      Many files:
        Added GPL copyright text
      Removed files:
        Docs/Support/colspec-fix.pl
        Docs/Support/docbook-fixup.pl
        Docs/Support/docbook-prefix.pl
        Docs/Support/docbook-split
        Docs/Support/make-docbook
        Docs/Support/make-makefile
        Docs/Support/test-make-manual
        Docs/Support/test-make-manual-de
        Docs/Support/xwf
      6523aca7
  5. 23 Dec, 2006 1 commit
  6. 19 Dec, 2006 1 commit
    • gkodinov/kgeorge@macbook.gmz's avatar
      Bug #23578: Corruption prevents Optimize table from working properly with a · 8e036791
      gkodinov/kgeorge@macbook.gmz authored
      spatial index
       While executing OPTIMIZE TABLE on MyISAM tables the server re-creates the
       index file(s) in order to sort them physically by the key. This cannot be 
       done for R-tree indexes as it makes no sense.
       The server was not checking the type of the index and was accessing an 
       R-tree index as if it was a B-tree.
       Fixed by preventing sorting the index file if it contains an R-tree index.  
       
      8e036791
  7. 25 Oct, 2006 1 commit
    • istruewing@chilla.local's avatar
      Bug#22119 - Changing MI_KEY_BLOCK_LENGTH makes a wrong myisamchk · 7dc7af51
      istruewing@chilla.local authored
      When compiling with a default key block size greater than the
      smallest key block size used in a table, checking that table
      failed with bogus errors. The table was marked corrupt. This
      affected myisamchk and the server.
      
      The problem was that the default key block size was used at
      some places where sizes less or equal to the block size of the
      index in check was required.
      
      We do now use the key block size of the particular index
      when checking.
      
      A test case is available for later versions only.
      7dc7af51
  8. 09 Oct, 2006 1 commit
    • istruewing@chilla.local's avatar
      Bug#8283 - OPTIMIZE TABLE causes data loss · 5f08a831
      istruewing@chilla.local authored
      OPTIMIZE TABLE with myisam_repair_threads > 1 performs a non-quick 
      parallel repair. This means that it does not only rebuild all 
      indexes, but also the data file.
      
      Non-quick parallel repair works so that there is one thread per 
      index. The first of the threads rebuilds also the new data file.
      
      The problem was that all threads shared the read io cache on the
      old data file. If there were holes (deleted records) in the table,
      the first thread skipped them, writing only contiguous, non-deleted
      records to the new data file. Then it built the new index so that
      its entries pointed to the correct record positions. But the other
      threads didn't know the new record positions, but put the positions
      from the old data file into the index.
      
      The new design is so that there is a shared io cache which is filled
      by the first thread (the data file writer) with the new contiguous
      records and read by the other threads. Now they know the new record
      positions.
      
      Another problem was that for the parallel repair of compressed
      tables a common bit_buff and rec_buff was used. I changed it so
      that thread specific buffers are used for parallel repair.
      
      A similar problem existed for checksum calculation. I made this
      multi-thread safe too.
      5f08a831
  9. 06 Sep, 2006 1 commit
  10. 04 Sep, 2006 1 commit
  11. 28 Jun, 2006 1 commit
    • ingo@mysql.com's avatar
      Bug#17877 - Corrupted spatial index · d8499f2d
      ingo@mysql.com authored
      CHECK TABLE could complain about a fully intact spatial index.
      A wrong comparison operator was used for table checking. 
      The result was that it checked for non-matching spatial keys. 
      This succeeded if at least two different keys were present, 
      but failed if only the matching key was present.
      
      I fixed the key comparison.
      d8499f2d
  12. 31 May, 2006 1 commit
  13. 10 Apr, 2006 1 commit
  14. 23 Nov, 2005 1 commit
  15. 01 Nov, 2005 1 commit
    • monty@mysql.com's avatar
      Review of new pushed code · 19502e8e
      monty@mysql.com authored
      Removed wrong fix for bug #14009 (use of abs() on null value causes problems with filesort)
      Mark that add_time(), time_diff() and str_to_date() can return null values
      19502e8e
  16. 26 Oct, 2005 1 commit
    • ingo@mysql.com's avatar
      1.2048 05/10/20 10:31:16 ingo@mysql.com +1 -0 · 5f51294a
      ingo@mysql.com authored
      Bug#12166 - Unable to index very large tables
      Moved clearing of errors behind the second repair attempt,
      but will clear only if no error happened.
      
      No test case. The error can be repeated with little free
      space on tmpdir only. I do not know of a way to create this
      in a portable way with our test suite.
      
      I did however attach a shell script to the bug report which
      can easily be adapted to the situation on the test machine.
      5f51294a
  17. 25 Oct, 2005 1 commit
  18. 24 Oct, 2005 1 commit
  19. 22 Oct, 2005 1 commit
  20. 21 Oct, 2005 1 commit
  21. 27 Sep, 2005 1 commit
  22. 23 Sep, 2005 1 commit
  23. 20 Sep, 2005 1 commit
  24. 09 Sep, 2005 1 commit
  25. 05 Sep, 2005 1 commit
  26. 09 Aug, 2005 1 commit
  27. 19 Jul, 2005 1 commit
    • ingo@mysql.com's avatar
      Bug#10932 - Building server with key limit of 128, makes test cases fail · ec15dda2
      ingo@mysql.com authored
      This patch allows to configure MyISAM for 128 indexes per table.
      The main problem is the key_map, wich is implemented as an ulonglong.
      To get rid of the limit and keep the efficient and flexible
      implementation, the highest bit is now used for all upper keys.
      This means that the lower keys can be disabled and enabled 
      individually as usual and the high keys can only be disabled and
      enabled as a block. That way the existing test suite is still
      applicable, while more keys work, though slightly less efficient.
      To really get more than 64 keys, some defines need to be changed.
      Another patch will address this.
      ec15dda2
  28. 03 Jun, 2005 2 commits
    • mronstrom@mysql.com's avatar
      Bug #10901 · 1eaacaf1
      mronstrom@mysql.com authored
      After review fix
      Copy from internal state to share state only when in lock write
      mode (happens only when lock table x write has been performed since
      update_state_info is only called when holding a TL_READ_NO_INSERT
      lock normally. Previous patch would have failed in combination with
      delayed writes.
      1eaacaf1
    • mronstrom@mysql.com's avatar
      Bug #10901 · 96252c1d
      mronstrom@mysql.com authored
      Analyze table corrupts the state on
      data_file_length, records, index_file_length...
      by writing the shared state when there is an updated internal
      state due to inserts or deletes
      Fixed by synching the shared state with the internal state before
      writing it to disk
      Added test cases of 2 error cases and a normal case in new
      analyze test case
      96252c1d
  29. 13 May, 2005 1 commit
  30. 11 Apr, 2005 1 commit
  31. 03 Jan, 2005 1 commit
  32. 18 Dec, 2004 1 commit
    • monty@mysql.com's avatar
      Add 0x before pointers (to help with debugging) · 3fb088a0
      monty@mysql.com authored
      Add support for VARCHAR with 1 or 2 length bytes
      Enable VARCHAR packing in MyISAM files (previous patch didn't pack data properly)
      Give error if we got problems in temporary tables during a SELECT
      Don't use new table generated by ALTER TABLE if index generation fails
      Fixed wrong call by range_end() (Could cause an ASSERT in debug mode)
      3fb088a0
  33. 06 Dec, 2004 2 commits
  34. 12 Nov, 2004 1 commit
  35. 11 Nov, 2004 1 commit
  36. 29 Oct, 2004 1 commit
  37. 22 Sep, 2004 1 commit
    • sergefp@mysql.com's avatar
      Fix for BUG#4785: · 6e0ba8e6
      sergefp@mysql.com authored
       * myisampack leaves key_file_length value from original table
       * myisamchk uses this value when calculating key file pointer length
      6e0ba8e6
  38. 03 Sep, 2004 1 commit