- 27 Sep, 2006 4 commits
-
-
andrey@example.com authored
into example.com:/work/mysql-5.1-runtime-fresh2
-
andrey@example.com authored
There was possible stack overrun in an edge case which handles invalid body of a SP in mysql.proc . That should be case when mysql.proc has been changed manually. Though, due to bug 21513, it can be exploited without having access to mysql.proc only being able to create a stored routine.
-
petr/cps@mysql.com/owlet.local authored
at the moment, so we can safely do that). Update an error mesage to make it translateable.
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-bug21414
-
- 26 Sep, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-runtime
-
- 25 Sep, 2006 5 commits
-
-
andrey@example.com authored
when set to DISABLED It was a silly ordering number error.
-
andrey@example.com authored
ALTER EVENT in stored procedure body led to a crash during the procedure call. Affected was only ALTER EVENT which changed the interval of the event. No problems with AT, STARTS, ENDS and so on.
-
andrey@example.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug22379_runtime/my51-bug22379_runtime
-
msvensson@neptunus.(none) authored
Remove race situations that occur when removing pidfiles. Primarily each process should remove its own pidfile, secondly it should be removed by the process that created it and _only_ if it's certain the process is dead. Third, mysql-test-run.pl will remove the pidfile when process has been killed. - Set state of an instance to STARTING _before_ calling instance->start() - Check that pidfile of instance has been created before changing STARTING => STARTED - Only remove the pidfile if IM kills an instance with SIGKILL, otherwise the instance will remove it itself
-
- 15 Sep, 2006 3 commits
-
-
petr/cps@owlet.local authored
into mysql.com:/home/cps/mysql/trees/5.1-runtime-new
-
petr/cps@mysql.com/owlet.local authored
Bug #18559 "log tables cannot change engine, and gets deadlocked when dropping w/ log on": 1) Add more generic error messages 2) Add new handlerton flag for engines, which support log tables 3) Remove (log-tables related) mutex lock in myisam to improve performance
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-rt-merge
-
- 14 Sep, 2006 3 commits
-
-
andrey@example.com authored
initialized prior to usage as well as deinitialized on shutdown.
-
dlenev@mockturtle.local authored
into mockturtle.local:/home/dlenev/src/mysql-5.1-rt-merge
-
andrey@example.com authored
5.1.12.
-
- 13 Sep, 2006 2 commits
-
-
ahristov@bk-internal.mysql.com authored
fix sigsegv
-
timour/timka@lamia.home authored
into lamia.home:/home/timka/mysql/src/5.1-dbg
-
- 12 Sep, 2006 16 commits
-
-
tsmith@maint2.mysql.com authored
into maint2.mysql.com:/data/localhome/tsmith/bk/mrg/51
-
andrey@example.com authored
-
timour/timka@lamia.home authored
The cause of the bug was an incomplete fix for bug 18080. The problem was that setup_tables() unconditionally reset the name resolution context to its 'tables' argument, which pointed to the first table of an SQL statement. The bug fix limits resetting of the name resolution context in setup_tables() only in the cases when the context was not set by earlier parser/optimizer phases.
-
msvensson@neptunus.(none) authored
Correct faulty merge, "mysql_priv.h" must be included for the ifdef WITH_INNOBASE_STORAGE_ENGINE to work
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
andrey@example.com authored
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.1-maint
-
Kristofer.Pettersson@naruto. authored
- When an ALTER TABLE RENAME is performed on windows, the files are closed and their cached file descriptors are marked invalid. Performing INSERT, UPDATE or SELECT on the associated merge table causes a server crash on windows. This patch adds a test for bad file descriptors when a table attempts a lock. If a bad descriptor is found an error is thrown. An additional FLUSH TABLES will be necessary to further operate on the associated merge table.
-
andrey@example.com authored
-
kroki/tomash@moonlight.intranet authored
The problem was that if after FLUSH TABLES WITH READ LOCK the user issued DROP/ALTER PROCEDURE/FUNCTION the operation would fail (as expected), but after UNLOCK TABLE any attempt to execute the same operation would lead to the error 1305 "PROCEDURE/FUNCTION does not exist", and an attempt to execute any stored function will also fail. This happened because under FLUSH TABLES WITH READ LOCK we couldn't open and lock mysql.proc table for update, and this fact was erroneously remembered by setting mysql_proc_table_exists to false, so subsequent statements believed that mysql.proc doesn't exist, and thus that there are no functions and procedures in the database. As a solution, we remove mysql_proc_table_exists flag completely. The reason is that this optimization didn't work most of the time anyway. Even if open of mysql.proc failed for some reason when we were trying to call a function or a procedure, we were setting mysql_proc_table_exists back to true to force table reopen for the sake of producing the same error message (the open can fail for number of reasons). The solution could have been to remember the reason why open failed, but that's a lot of code for optimization of a rare case. Hence we simply remove this optimization.
-
andrey@example.com authored
Remove SHOW SCHEDULER STATUS command and migrate the information output to `mysqladmin debug` (COM_DEBUG) SHOW SCHEDULER STATUS was introduced in 5.1.11, provided some debug information about event scheduler internals and was enabled only in debug builds.
-
rburnett@production.mysql.com authored
Fixing failed merge
-
cmiller@maint1.mysql.com authored
More specifically, the scripts/Makefile isn't created and it doesn't translate mysql_fix_privilege_tables ".sh" . So, mysql-test/mysql-test-run.pl doesn't find the binary and substitutes /bin/false instead. That obviously doesn't "fix" anything and the test fails because of it.
-
- 11 Sep, 2006 2 commits
-
-
rburnett@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-kt
-
msvensson@shellback.(none) authored
-
- 09 Sep, 2006 2 commits
-
-
serg@janus.mylan authored
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/mysql-5.1-arch
-
- 08 Sep, 2006 2 commits
-
-
msvensson@shellback.(none) authored
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-