- 04 Feb, 2005 15 commits
-
-
marko@hundin.mysql.fi authored
by adding #ifndef UNIV_HOTBACKUP and adjusting some function declarations.
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/mysql-5.0
-
msvensson@neptunus.homeip.net authored
into neptunus.homeip.net:/home/msvensson/mysql/mysql-5.0-cluster-extra
-
msvensson@neptunus.homeip.net authored
-
marko@hundin.mysql.fi authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
guilhem@mysql.com authored
Proposal to fix this problem: when using libmysqlclient, you must call mysql_server_end() to nicely free memory at the end of your program; it however sounds weird to call a function named *SERVER_end* when you're the CLIENT (you're not ending the server, you're ending your ability to talk to servers). So here I add two defines which should be more generic names. This was longly discussed with Konstantin, Serg, Brian. The problem started from a post on valgrind-users list: http://sourceforge.net/mailarchive/forum.php?thread_id=5778035&forum_id=32038 ; our manual mentions these functions only for libmysqld API so needs some fixing, and then we can close BUG#8099 and BUG#6149.
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0
-
ramil@mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-compile
-
msvensson@neptunus.homeip.net authored
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0
-
ramil@mysql.com authored
-
pekka@mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-perl
-
- 03 Feb, 2005 25 commits
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
into pcgem.rdg.cyberkinetica.com:/var/db/bk/work-acurtis/bug8057
-
acurtis@pcgem.rdg.cyberkinetica.com authored
into pcgem.rdg.cyberkinetica.com:/var/db/bk/work-acurtis/bug6726
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Fix and test for parse bug
-
pekka@mysql.com authored
-
acurtis@pcgem.rdg.cyberkinetica.com authored
into pcgem.rdg.cyberkinetica.com:/var/db/bk/work-acurtis/bug8057
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Fix crash with LAST_INSERT_ID() in UPDATE, Tests included,
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-perl
-
kent@mysql.com authored
new file
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
guilhem@mysql.com authored
-
mikael@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/export/home/mikael/mysql-5.0
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-compile
-
mikael@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/export/home/mikael/mysql-4.1
-
kent@mysql.com authored
Let --start-and-exit actually start a server Added that test case names can be specified on the comman line Added embedded server support Added environment variables UMASK, UMASK_DIR Added missing MASTER_MYSOCK1, MASTER_MYPORT1, USE_RUNNING_SERVER Added missing CHARSETSDIR, MYSQL_FIX_SYSTEM_TABLES, MYSQL_CLIENT_TEST Pass on return value from sleep_until_file_created(), to fail test Fail test if early termination of mysqld servers Create intial databases for the second master, and two additional slaves mtr_process.pl: Find out if port is still in use, using simple TCP connect Use non blocking waitpid() to catch terminations early Make a special case spawning the 'mysqltest' application Redo the fork() if it returns EAGAIN Make sure to record if master or slave terminated Improved debugging output Improved code that remove PID files to avoid race Abort if we can't stop all mysqld servers using our ports Many improvements in killing mysqld servers Let sleep_until_file_created() catch if server died early mtr_report.pl: Added option to disable test cases using <testcase>.disabled file If --timer, only try to open file with time data if it exists mtr_io.pl: Remove starting/ending space reading server options from file
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
mronstrom@mysql.com authored
into mysql.com:/Users/mikron/mysql-4.1
-
mronstrom@mysql.com authored
into mysql.com:/Users/mikron/mysql-5.0
-
mysqldev@mysql.com authored
into mysql.com:/home/mysqldev/tulin/mysql-5.0
-
tulin@mysql.com authored
-
mysqldev@mysql.com authored
into mysql.com:/home/mysqldev/tulin/mysql-5.0
-
tulin@mysql.com authored
-
mysqldev@mysql.com authored
-
monty@mysql.com authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
guilhem@mysql.com authored
we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
-