1. 12 Oct, 2005 5 commits
    • unknown's avatar
      Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-4.1 · 228d5c42
      unknown authored
      into moonbone.local:/work/13535-bug-4.1-mysql
      
      
      mysql-test/r/select.result:
        Auto merged
      mysql-test/t/select.test:
        Auto merged
      228d5c42
    • unknown's avatar
      merge · 61dfc334
      unknown authored
      61dfc334
    • unknown's avatar
      Fix for BUG#13023: "SQL Thread is up but doesn't move forward". Details in slave.cc; · 7ff27a61
      unknown authored
      in short we now record whenever the slave I/O thread ignores a master's event because of its server id,
      and use this info in the slave SQL thread to advance Exec_master_log_pos. Because if we
      do not, this variable stays at the position of the last executed event, i.e. the last *non-ignored*
      executed one, which may not be the last of the master's binlog (and so the slave *looks* behind
      the master though it's data-wise it's not).
      
      
      mysql-test/t/rpl_dual_pos_advance-master.opt:
        empty; its goal is just to trigger a server restart after running the test,
        so that the master forgets that it was a slave (otherwise it affects the following tests).
      sql/log.cc:
        No more default arguments for Rotate_log_event constructor.
        MYSQL_LOG::appendv() is now called without mutex.
      sql/log_event.cc:
        Moving one Rotate_log_event constructor from log_event.h. Support for on-demand choice of
        duplicating the string argument of the constructor or not (because there now are needs for both
        alternatives, see slave.cc).
      sql/log_event.h:
        We now have a case where a Rotate_log_event is executed by the slave SQL thread while
        not being in the relay log, so it needs to pretend its length is 0: a ZERO_LEN flag for that;
        a flag DUP_NAME (replaces "bool alloced") to be able to choose if we want the constructor
        to duplicate the string argument or not.
      sql/slave.cc:
        A comment for BUG#13861 (to be fixed). llstr() instead of %ld as the number is ulonglong.
        mi->rli becomes rli in some places.
        Fix for BUG#13023:
        - in the slave I/O thread, whenever we ignore an event because of its server id we update
        a couple of coordinates in memory
        - in the slave SQL thread, whenever we bump into the end of the latest relay log, we check
        this couple of coordinates to see if we should advance our Exec_master_log_pos.
        - when the slave I/O thread terminates it saves these in-memory coordinates into a Rotate event
        in the relay log, so that they are durable.
      sql/slave.h:
        A couple of coordinates in RELAY_LOG_INFO to keep track of the last ignored events received
        by the slave I/O thread (ignored because of the server id).
      mysql-test/r/rpl_dual_pos_advance.result:
        New BitKeeper file ``mysql-test/r/rpl_dual_pos_advance.result''
      mysql-test/t/rpl_dual_pos_advance.test:
        Test for BUG#13023 (with a part, disabled, to test BUG#13861 when I fix it).
        Before the fix, this test used to hang.
      7ff27a61
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 9af6650a
      unknown authored
      into  mysql.com:/users/grog/4.1
      
      
      9af6650a
    • unknown's avatar
      sql_yacc.yy: · be559ad6
      unknown authored
        Bug #10308: Parse 'purge master logs' with subselect correctly.
      subselect.test:
        Bug #10308: Test for 'purge master logs' with subselect.
      subselect.result:
        Bug #10308: Test result for 'purge master logs' with subselect.
      
      
      mysql-test/r/subselect.result:
        Bug #10308: Test result for 'purge master logs' with subselect.
      mysql-test/t/subselect.test:
        Bug #10308: Test for 'purge master logs' with subselect.
      sql/sql_yacc.yy:
        Bug #10308: Parse 'purge master logs' with subselect correctly.
      be559ad6
  2. 11 Oct, 2005 4 commits
  3. 10 Oct, 2005 4 commits
  4. 08 Oct, 2005 2 commits
  5. 07 Oct, 2005 7 commits
    • unknown's avatar
      Merge mysqldev@production.mysql.com:my/mysql-4.1-release · 30d81f00
      unknown authored
      into  mysql.com:/usr/home/ram/work/mysql-4.1
      
      
      scripts/make_binary_distribution.sh:
        Auto merged
      30d81f00
    • unknown's avatar
      d1e71faf
    • unknown's avatar
      Copy zlib.a and valgrind.supp if exists. · d40a0f42
      unknown authored
      Copy disabled.def
      (Backport of Kent's change from the main tree to the 4.1.15 build clone.
      Original changeset:  2005/10/07 13:08:07+02:00 kent@mysql.com )
      
      
      scripts/make_binary_distribution.sh:
        Copy zlib.a and valgrind.supp if exists.
        Copy disabled.def
        (Backport of Kent's change from the main tree to the 4.1.15 build clone.)
      d40a0f42
    • unknown's avatar
      make_binary_distribution.sh: · c533a6bf
      unknown authored
        Copy zlib.a and valgrind.supp if exists
        Copy disabled.def
      
      
      scripts/make_binary_distribution.sh:
        Copy zlib.a and valgrind.supp if exists
      c533a6bf
    • unknown's avatar
      Increase the version number. · 8b1936fa
      unknown authored
      8b1936fa
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 0ecbc17c
      unknown authored
      into  mysql.com:/home/my/mysql-4.1
      
      
      0ecbc17c
    • unknown's avatar
      Review of new code since last pull · 3dcf2056
      unknown authored
      - Use %lx instead of %p as %p is not portable
      - Don't replace ROW item with Item_null
      
      
      myisam/mi_rkey.c:
        Use %lx instead of %p as %p is not portable
      myisam/mi_search.c:
        Use %lx instead of %p as %p is not portable
      mysql-test/r/select.result:
        More test for ROW comparison
      mysql-test/t/select.test:
        More test for ROW comparison
      sql/item.cc:
        We can't replace a ROW item with Item_null because:
        - Arg_comparator is still using the orignal row items and it's not good to have args[0] different from what is actually compared
        - If we are using the <=> comparator, NULL can still be compared as true
        - We would break things if we would ever use resolve_const_item() for operators like >, < etc.
      3dcf2056
  6. 06 Oct, 2005 9 commits
  7. 05 Oct, 2005 5 commits
  8. 04 Oct, 2005 2 commits
  9. 03 Oct, 2005 2 commits
    • unknown's avatar
      Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.1 · 319dd6ae
      unknown authored
      into  hundin.mysql.fi:/home/marko/mysql-4.1
      
      
      319dd6ae
    • unknown's avatar
      Fix bug#13535 Incorrect result from SELECT statement after SHOW TABLE STATUS · 78e8833f
      unknown authored
      After SHOW TABLE STATUS last_insert_id wasn't cleaned, and next select
      erroneously rewrites WHERE condition and returs a row;
      5.0 isn't affected because of different SHOW TABLE STATUS handling.
      
      last_insert_id cleanup added to mysqld_extend_show_tables().
      
      
      sql/sql_show.cc:
        Fix bug #13535 Incorrect result from SELECT statement after SHOW TABLE STATUS
        Added last_insert_id cleanup after SHOW TABLE STATUS command.
      mysql-test/t/select.test:
        Test case for bug #13535 Incorrect result from SELECT statement after SHOW TABLE STATUS
      mysql-test/r/select.result:
        Test case for bug #13535 Incorrect result from SELECT statement after SHOW TABLE STATUS
      78e8833f