An error occurred fetching the project authors.
  1. 13 Aug, 2008 3 commits
  2. 12 Aug, 2008 10 commits
  3. 11 Aug, 2008 16 commits
    • Davi Arnaut's avatar
      Bug#38486: Crash when using cursor protocol · d5620961
      Davi Arnaut authored
      Post-merge fix: mysql_client_test.c is compiled by C compilers
      and some C compilers don't support mixed declarations and code
      and it's explicitly forbidden by ISO C90.
      d5620961
    • Marc Alff's avatar
      Manual merge of mysql-5.0-bugteam -> mysql-5.1-bugteam · 385b4bf7
      Marc Alff authored
      Note: NULL merge of sql/sql_yacc.yy, the fix for bug#38296 will be provided separately for 5.1
      385b4bf7
    • Marc Alff's avatar
      Merge mysql-5.0-bugteam -> local bugfix branch · e087c05d
      Marc Alff authored
      e087c05d
    • Marc Alff's avatar
      Bug#37302 (missing DBUG_RETURN macro in function "find_key_block" (5.0 only)) · fd324dd3
      Marc Alff authored
      Fixed missing DBUG_RETURN in the function find_key_block
      fd324dd3
    • Mattias Jonsson's avatar
      1e73141b
    • Mattias Jonsson's avatar
      Bug#20129: ALTER TABLE ... REPAIR PARTITION ... complains that · 07e9a6dc
      Mattias Jonsson authored
      partition is corrupt
      
      The main problem was that ALTER TABLE t ANALYZE/CHECK/OPTIMIZE/REPAIR
      PARTITION took another code path (over mysql_alter_table instead of
      mysql_admin_table) which differs in two ways:
      1) alter table opens the tables in a different way than admin tables do
         resulting in returning with error before it tried the command
      2) alter table does not start to send any diagnostic rows to the client
         which the lower admin functions continue to use -> resulting in
         assertion crash
      
      The fix:
      Remapped ALTER TABLE t ANALYZE/CHECK/OPTIMIZE/REPAIR PARTITION to use
      the same code path as ANALYZE/CHECK/OPTIMIZE/REPAIR TABLE t.
      Adding check in mysql_admin_table to setup the partition list for
      which partitions that should be used.
      
      
      Partitioned tables will still not work with
      REPAIR TABLE/PARTITION USE_FRM, since that requires moving partitions
      to tables, REPAIR TABLE t USE_FRM, and check that the data still
      fulfills the partitioning function and then move the table back to
      being a partition.
      
      NOTE: I have removed the following functions from the handler
      interface:
      analyze_partitions, check_partitions, optimize_partitions,
      repair_partitions
      Since they are not longer needed.
      THIS ALTERS THE STORAGE ENGINE API
      07e9a6dc
    • Chad MILLER's avatar
      Merge from bugteam 5.0 trunk. · 318d288a
      Chad MILLER authored
      318d288a
    • Marc Alff's avatar
      Bug#38296 (low memory crash with many conditions in a query) · 394691cd
      Marc Alff authored
      This fix is for 5.0 only : back porting the 6.0 patch manually
      
      The parser code in sql/sql_yacc.yy needs to be more robust to out of
      memory conditions, so that when parsing a query fails due to OOM,
      the thread gracefully returns an error.
      
      Before this fix, a new/alloc returning NULL could:
      - cause a crash, if dereferencing the NULL pointer,
      - produce a corrupted parsed tree, containing NULL nodes,
      - alter the semantic of a query, by silently dropping token values or nodes
      
      With this fix:
      - C++ constructors are *not* executed with a NULL "this" pointer
      when operator new fails.
      This is achieved by declaring "operator new" with a "throw ()" clause,
      so that a failed new gracefully returns NULL on OOM conditions.
      
      - calls to new/alloc are tested for a NULL result,
      
      - The thread diagnostic area is set to an error status when OOM occurs.
      This ensures that a request failing in the server properly returns an
      ER_OUT_OF_RESOURCES error to the client.
      
      - OOM conditions cause the parser to stop immediately (MYSQL_YYABORT).
      This prevents causing further crashes when using a partially built parsed
      tree in further rules in the parser.
      
      No test scripts are provided, since automating OOM failures is not
      instrumented in the server.
      Tested under the debugger, to verify that an error in alloc_root cause the
      thread to returns gracefully all the way to the client application, with
      an ER_OUT_OF_RESOURCES error.
      394691cd
    • Chad MILLER's avatar
      null-merge of backported changes. · cf43a69a
      Chad MILLER authored
      cf43a69a
    • Chad MILLER's avatar
      fe39a901
    • Mattias Jonsson's avatar
      merge into an updated 5.1-bugteam tree · 854e2307
      Mattias Jonsson authored
      854e2307
    • Davi Arnaut's avatar
      44a16259
    • Davi Arnaut's avatar
      bafa07b2
    • Kristofer Pettersson's avatar
      f9e90f18
    • Kristofer Pettersson's avatar
      Automerge · a3b0b7bb
      Kristofer Pettersson authored
      a3b0b7bb
    • Kristofer Pettersson's avatar
      Bug#38486 Crash when using cursor protocol · 9fc39adf
      Kristofer Pettersson authored
                  
      Server side cursors were not initialized properly and this caused a reference to
      uninitialized memory.
      9fc39adf
  4. 07 Aug, 2008 4 commits
  5. 06 Aug, 2008 5 commits
  6. 04 Aug, 2008 1 commit
  7. 01 Aug, 2008 1 commit
    • Davi Arnaut's avatar
      Bug#37003: Tests sporadically crashes with embedded server · 9f550e6f
      Davi Arnaut authored
      Post-merge fix: Alter linking order so that the thread linking
      flags appear last in the list. This needs to be done this way
      because some linkers will not search the thread archive again
      if a undefined symbol (pthread_kill in this case) appears later.
      9f550e6f