An error occurred fetching the project authors.
  1. 21 Dec, 2003 1 commit
  2. 19 Dec, 2003 2 commits
  3. 17 Dec, 2003 1 commit
  4. 08 Dec, 2003 1 commit
  5. 04 Dec, 2003 2 commits
  6. 28 Nov, 2003 1 commit
    • guilhem@mysql.com's avatar
      In the slave I/O thread (in master.info), it seems less worse to flush · c9fd311a
      guilhem@mysql.com authored
      the relay log before flushing master.info.
      Doing 'before' leads to duplicate event, doing after leads to missing event.
      Both can be as destructive, but 'duplicate' enables us to later add detection
      code to catch it. Whereas 'missing' can't be caught (it can't, because
      the I/O thread can produce legal position jumps, for example if it has
      ignored an event coming from this slave (rememember that starting from 4.1.1,
      the I/O thread filters the server id). 
      c9fd311a
  7. 23 Nov, 2003 1 commit
    • guilhem@gbichot2's avatar
      Replication: · 05e5a35b
      guilhem@gbichot2 authored
      Now the I/O thread (in flush_master_info()) flushes the relay log to disk
      after reading every event. Slower but provides additionnal safety in case
      of brutal crash.
      I had to make the flush optional (i.e. add a if(some_bool_argument) in the function)
      because sometimes flush_master_info() is called when there is no usable
      relay log (the relay log's IO_CACHE is not initialized so can't be flushed).
      05e5a35b
  8. 22 Nov, 2003 1 commit
  9. 21 Nov, 2003 1 commit
  10. 20 Nov, 2003 1 commit
  11. 03 Nov, 2003 1 commit
    • guilhem@mysql.com's avatar
      When we delete the slave's temp tables from memory, we reset · fbc54c13
      guilhem@mysql.com authored
      rli->save_temporary_tables and slave_open_temp_tables
      (in old 4.0 you could make "SHOW STATUS LIKE 'slave_open_temp_tables'" grow
      indefinitely by doing RESET SLAVE and replicating always the same CREATE
      TEMPORARY TABLE).
      It's critical to reset save_temporary_tables to 0 (otherwise you may later
      read memory which has been freed) so this changeset should go into 4.1.
      fbc54c13
  12. 31 Oct, 2003 1 commit
    • guilhem@mysql.com's avatar
      4 small items in this: · c1f7f339
      guilhem@mysql.com authored
      - when we don't have in_addr_t, use uint32.
      - a forgotten initialization of slave_proxy_id in sql/log_event.cc (was not really "forgot", was
      "we needn't init it there", but there was one case where we needed...).
      - made slave_proxy_id always meaningful in THD and Log_event, so we can
      rely more on it (no need to test if it's meaningful). THD::slave_proxy_id
      is equal to THD::thread_id except for the slave SQL thread.
      - clean up the slave's temporary table (i.e. free their memory) when slave
      server shuts down.
      c1f7f339
  13. 29 Oct, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#1686 · 59d0872a
      guilhem@mysql.com authored
      "If 2 master threads with same-name temp table, slave makes bad binlog"
      and (two birds with one stone) for
      BUG#1240 "slave of slave breaks when STOP SLAVE was issud on parent slave
      and temp tables".
      
      Here is the design change:
      in a slave running with --log-slave-updates, events are now logged with the
      thread id they had on the master. So no more id conflicts between master threads,
      but introduces id conflicts between one master thread and one normal 
      client thread connected to the slave. This is solved by storing the server id
      in the temp table's name.
      
      New test which requires mysql-test-run to be run with --manager,
      otherwise it will be skipped.
      
      Undoing a Monty's change (hum, a chill runs down my spine ;) which was
      "Cleanup temporary tables when slave ends" in ChangeSet 1.1572.1.1.
      59d0872a
  14. 16 Oct, 2003 1 commit
  15. 15 Oct, 2003 1 commit
  16. 11 Oct, 2003 1 commit
  17. 09 Oct, 2003 1 commit
  18. 08 Oct, 2003 2 commits
    • guilhem@gbichot2's avatar
      Final push for WL#1098: · c0075fa6
      guilhem@gbichot2 authored
      "Add a column "Timestamp_of_last_master_event_executed" in SHOW SLAVE STATUS".
      Finally this is adding
      - Slave_IO_State (a copy of the State column of SHOW PROCESSLIST for the I/O thread,
      so that the users, most of the time, has enough info with only SHOW SLAVE STATUS).
      - Seconds_behind_master. When the slave connects to the master it does SELECT UNIX_TIMESTAMP()
      on the master, computes the absolute difference between the master's and the slave's clock.
      It records the timestamp of the last event executed by the SQL thread, and does a
      small computation to find the number of seconds by which the slave is late.
      c0075fa6
    • monty@narttu.mysql.fi's avatar
      Fixes after merge · d9ff6651
      monty@narttu.mysql.fi authored
      d9ff6651
  19. 19 Sep, 2003 1 commit
    • hf@deer.(none)'s avatar
      SCRUM · a2dbfaef
      hf@deer.(none) authored
      embedded library
      hash_insert renamed to my_hash_insert to avoid name intersection
      with another libraries
      is there better idea?
      a2dbfaef
  20. 13 Sep, 2003 1 commit
  21. 12 Sep, 2003 1 commit
    • guilhem@mysql.com's avatar
      Quick backport of the following bugfix from MySQL 4.0.14. · 40a88045
      guilhem@mysql.com authored
      DO NOT COPY THIS CODE TO 4.0. The bugfix is better in 4.0,
      but here in 3.23 we don't want to add a new error code so
      we just use ER_EMPTY_QUERY. Bug was:
      "If a query was ignored on the slave (because of
      @code{replicate-ignore-table} and other similar rules), the slave
      still checked if the query got the same error code (0, no error) as on
      the master. So if the master had an error on the query (for example,
      ``Duplicate entry'' in a multiple-row insert), then the slave stopped
      and warned that the error codes didn't match. (Bug #797)"
      40a88045
  22. 11 Sep, 2003 2 commits
  23. 03 Sep, 2003 1 commit
  24. 01 Sep, 2003 1 commit
    • dlenev@dlenev.mshome's avatar
      Implemented replication over SSL · 2486222c
      dlenev@dlenev.mshome authored
       Added proper options to CHANGE MASTER TO, new fields to SHOW SLAVE STATUS,
       Honoring this parameters during connection to master.
       Introduced new format of master.info file
      2486222c
  25. 27 Aug, 2003 1 commit
  26. 25 Aug, 2003 2 commits
  27. 23 Aug, 2003 2 commits
  28. 21 Aug, 2003 1 commit
  29. 20 Aug, 2003 1 commit
    • guilhem@mysql.com's avatar
      First commit for fixing BUG#1100 · 1dd53ed0
      guilhem@mysql.com authored
      "LOAD DATA INFILE is badly filtered by binlog-*-db rules".
      There will probably be a second final one to merge Dmitri's changes
      to rpl_log.result and mine.
      2 new tests:
      rpl_loaddata_rule_m : test of logging of LOAD DATA INFILE when the master has binlog-*-db rules,
      rpl_loaddata_rule_s : test of logging of LOAD DATA INFILE when the slave has binlog-*-db rules and --log-slave-updates.
      1dd53ed0
  30. 19 Aug, 2003 2 commits
  31. 18 Aug, 2003 1 commit
    • monty@mashka.mysql.fi's avatar
      After merge fixes · 4f751216
      monty@mashka.mysql.fi authored
      Use server character set if --default-character-set is not used
      Added convert_string() for more efficient alloc+character-set convert of strings
      4f751216
  32. 07 Aug, 2003 1 commit
  33. 04 Aug, 2003 1 commit
    • guilhem@mysql.com's avatar
      2 bugfixes: · bb12d905
      guilhem@mysql.com authored
      - Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
      Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
      for that.
      - Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
      SLAVE STATUS". Now these reset the errors.
      bb12d905