An error occurred fetching the project authors.
- 19 Dec, 2003 1 commit
-
-
guilhem@gbichot2 authored
* A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1.
-
- 16 Dec, 2003 1 commit
-
-
monty@mysql.com authored
Make ENGINE= an alias for TYPE= (Compabiltiy with 4.1) Fix when using symlinked data files and realpath() is not working
-
- 17 Oct, 2003 2 commits
-
-
guilhem@mysql.com authored
to enable SHOW SLAVE STATUS again.
-
guilhem@mysql.com authored
-
- 16 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
while the slave is connected.
-
- 09 Oct, 2003 1 commit
-
-
guilhem@gbichot2 authored
I manually edited rpl_openssl.result because the test is skipped on my machine. Hope it's correct.
-
- 08 Oct, 2003 2 commits
-
-
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.
-
monty@narttu.mysql.fi authored
-
- 07 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
as the test is meaningful only if the slave supports transactions, we require this. As in 4.0 the slave runs with --skip-innodb, we test for BDB.
-
- 03 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
Rotate_log_event::exec_event() believed that the relay log was corrupted. Fixed it by moving the test for corruption to Start_log_event::exec_event(). Changed Rotate_log_event::exec_event() to not increment positions when the event is seen in the middle of a transaction. I did a separate commit in 4.1 (so this should not be merged to 4.0) because code is a bit different in 4.1. A test to see if the slave detects when the master died while writing a transaction to the binlog (uses a forged truncated binlog I made).
-