6 commits

Author	SHA1	Message	Date
dlenev@brandersnatch.localdomain	067b2e3bb0	Moved testing of binlog_cache_use/binlog_cache_disk_use statistical variables from ... rpl_relayrotate.test to innodb.test since this test requires innodb support.	2004-05-19 17:43:50 +04:00
dlenev@jabberwock.localdomain	a80f46bfdf	WL#775 "Add status variable identifying binlog_cache_size shortage" ... Added two status variables: binlog_cache_use - counts number of transactions that used somehow transaction temporary binary log. binlog_cache_disk_use - counts number of transactions that required disk I/O for storing info in this this binary log.	2004-04-02 00:47:20 +04:00
antony@ltantony.rdg.cyberkinetica.homeunix.net	fcf96dbb18	WorkLog#1323 ... Deprecate the use of TYPE=... Preferred syntax is ENGINE=	2003-12-10 04:31:42 +00:00
guilhem@gbichot2	6bbf52d2ac	Fix for a rpl_relayrotate failure. ... Changed Rotate_log_event::exec_event() to not increment positions when the event is seen in the middle of a transaction.	2003-10-03 20:07:08 +02:00
guilhem@mysql.com	3ac3252a65	Cleaning DROP TABLE which is important if the tests are run in a certain order. ... This is because rpl_relayrotate.test uses InnoDB. Example of a failing sequence: rpl_relayrotate.test repl_user_variables.test rpl_relayrotate.test Explaination in the files. Btw all other tests which use InnoDB (innodb*.test) already have this final DROP TABLE. Removed a wrong comment of mine.	2003-05-22 22:29:44 +02:00
guilhem@mysql.com	b03ec0d7db	Replication: new code to not modify in-memory log positions until the COMMIT ... is executed, even if the transaction spans on >=2 relay logs (bug #53). New variable relay_log_purge =0|1 New test to verify bug #53	2003-04-24 15:29:25 +02:00