- 22 Nov, 2008 1 commit
-
-
Vladislav Vaintroub authored
-
- 14 Nov, 2008 1 commit
-
-
Vladislav Vaintroub authored
status The problem appears to be a race condition, when service is being stopped right after startup. We set the service status to SERVICE_RUNNING way too early it cannot yet handle stop requests - initialization has not finished and hEventShutdown that signals server to stop is not yet created. If somebody issues "net stop MySQL" at this time, MySQL is not informed about the stop and continues to run as usual, while NTService::ServiceMain() stucks forever waiting for mysql's "main" thread to finish. Solution is to remain in SERVICE_START_PENDING status until after server initialization is fully complete and only then change the status to SERVICE_RUNNING. In SERVICE_START_PENDING we do not accept service control requests, i.e it is not possible to stop service in that time.
-
- 10 Nov, 2008 2 commits
-
-
Vladislav Vaintroub authored
-
Vladislav Vaintroub authored
japanese characters. Fix - removed obsolvete setlocale from my_init.c . In MBCS environments it caused unwanted character-to-byte translations in fputc() in client code and wrong output as result.
-
- 07 Nov, 2008 3 commits
-
-
Matthias Leich authored
-
Kristofer Pettersson authored
-
Kristofer Pettersson authored
Innodb monitor could cause a server crash because of invalid access to a shared variable in a concurrent environment. This patch adds a guard to protect against crashes but not against inconsistent values because of performance reasons.
-
- 06 Nov, 2008 17 commits
-
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Matthias Leich authored
where it was forgotten to remove them.
-
kent.boortz@sun.com authored
-
Andrei Elkin authored
refining the regression test to avoid explicit innodb engine in create.
-
Joerg Bruehe authored
-
Joerg Bruehe authored
-
Joerg Bruehe authored
Prevent this by modifying CFLAGS and CXXFLAGS. Upmerge from 5.0, modified according to the different spec file structure.
-
Joerg Bruehe authored
Prevent this by modifying CFLAGS and CXXFLAGS.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Mattias Jonsson authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Sven Sandberg authored
Problem 1: BUG#36625: rpl_redirect doesn't do anything useful. It tests an obsolete feature that was never fully implemented. Fix 1: Remove rpl_redirect. Problem 2: rpl_innodb_bug28430 and rpl_flushlog_loop are disabled despite the bugs for which they were disabled have been fixed. Fix 2: Re-enable rpl_innodb_bug28430 and rpl_flushlog_loop.
-
Mattias Jonsson authored
-
- 05 Nov, 2008 7 commits
-
-
Mattias Jonsson authored
-
Evgeny Potemkin authored
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-
Evgeny Potemkin authored
The convert_constant_item function converts a constant to integer using field for condition like 'field = a_constant'. In some cases the convert_constant_item is called for a subquery when outer select is already being executed, so convert_constant_item saves field's value to prevent its corruption. For EXPLAIN and at the prepare phase field's value isn't initialized yet, thus when convert_constant_item tries to restore saved value it fails assertion. Now the convert_constant_item doesn't save/restore field's value if it's haven't been read yet. Outer constant values are always saved.
-
Mattias Jonsson authored
-
Mattias Jonsson authored
order by Problem was that the first index read was unordered, and the next was ordered, resulting in use of uninitialized data. Solution was to use the correct variable to see if the 'next' call should be ordered or not.
-
- 04 Nov, 2008 9 commits
-
-
Matthias Leich authored
-
Joerg Bruehe authored
-
Mattias Jonsson authored
-
Matthias Leich authored
Bug#39848 events_bugs fails sporadically on pushbuild (missing rows in table event_log) Details: Reimplement the subtest for BUG 28924 - check if the number of rows within the table event_log changes but don't print rows because the number varies depending on load on testing box - shift DROP USER befor DROP EVENT = Subtest fits again to old bug - remove no more needed comments + variables Bug#39863 events_bugs fails sporadically on pushbuild (extra processes in I_S.PROCESSLIST) Details: Abort with appropriate message to the protocol if release_lock() does not has the intended effect. This cannot prevent problems caused by the probably buggy release_lock() but it reveals if we had a problem in this area. Bug#39978 main.events_bugs does not clean up Detail: Restore global.event_scheduler = ON at end of test Bug#39569 events_bugs fails sporadically on pushbuild (should have failed with errno 1539) Detail: Set $wait_timeout to 4 instead of 2 - Fix two instabilities (result sets pulled from processlist in subtest for bug 16407) which were found during tests with high parallel I/O load - Minor improvements of formatting Details: - Add comments - Remove tabs and trailing blanks - Add line breaks for better readability
-
Andrei Elkin authored
updating two test results.
-
Kristofer Pettersson authored
-
Tatiana A. Nurnberg authored
correct text describing the --plugin-load option to mysqld
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-