- 23 Feb, 2007 4 commits
-
-
anozdrin/alik@alik.opbmk authored
into alik.opbmk:/mnt/raid/alik/MySQL/devel/5.1-rt-build
-
anozdrin/alik@alik.opbmk authored
which accidentally got broken during the merge on 16-Feb-2007.
-
anozdrin/alik@alik.opbmk authored
into alik.opbmk:/mnt/raid/alik/MySQL/devel/5.1-rt
-
anozdrin/alik@alik.opbmk authored
Fix timeouts. Only test suite is changed.
-
- 22 Feb, 2007 4 commits
-
-
anozdrin/alik@alik.opbmk authored
-
anozdrin/alik@alik.opbmk authored
into alik.opbmk:/mnt/raid/alik/MySQL/devel/5.1-rt-merge
-
anozdrin/alik@alik.opbmk authored
-
kostja@bodhi.local authored
-
- 21 Feb, 2007 1 commit
-
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.1-runtime
-
- 20 Feb, 2007 5 commits
-
-
anozdrin/alik@alik.opbmk authored
The cause of im_daemon_life_cycle.imtest random failures was the following behaviour of some implementations of LINUX threads: let's suppose that a process has several threads (in LINUX threads, there is a separate process for each thread). When the main process gets killed, the parent receives SIGCHLD before all threads (child processes) die. In other words, the parent receives SIGCHLD, when its child is not completely dead. In terms of IM, that means that IM-angel receives SIGCHLD when IM-main is not dead and still holds some resources. After receiving SIGCHLD, IM-angel restarts IM-main, but IM-main failed to initialize, because previous instance (copy) of IM-main still holds server socket (TCP-port). Another problem here was that IM-angel restarted IM-main only if it was killed by signal. If it exited with error, IM-angel thought it's intended / graceful shutdown and exited itself. So, when the second instance of IM-main failed to initialize, IM-angel thought it's intended shutdown and quit. The fix is 1. to change IM-angel so that it restarts IM-main if it exited with error code; 2. to change IM-main so that it returns proper exit code in case of failure.
-
anozdrin/alik@alik.opbmk authored
1. use MySQL headers instead of system ones; 2. move logical part of code into a separate function.
-
anozdrin/alik@alik.opbmk authored
-
anozdrin/alik@booka. authored
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-5.1-runtime
-
- 19 Feb, 2007 8 commits
-
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-5.1-runtime
-
thek@kpdesk.mysql.com authored
- Merged from 5.0 - Removed redundant call to set_time(); now included in init_for_queries
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-5.0-runtime
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/bug23240/my51-bug23240
-
thek@kpdesk.mysql.com authored
- Starting time of a query sent by bootstrapping wasn't initialized and starting time defaulted to 0. This later used value by NOW- item and was translated to 1970-01-01 11:00:00. - Marketing the time with thd->set_time() before the call to mysql_parse resolves this issue. - set_time was refactored to be part of the thd->init_for_queries- process.
-
kostja@bodhi.local authored
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/bug23240/my50-bug23240
-
thek@kpdesk.mysql.com authored
- Starting time of a query sent by file bootstrapping wasn't initialized and starting time defaulted to 0. This later used value by the Now- item and is translated to 1970-01-01 11:00:00. - marking the time with thd->set_time() before the call to mysql_parse resolves this issue.
-
- 18 Feb, 2007 1 commit
-
-
anozdrin/alik@alik.opbmk authored
im_daemon_life_cycle fails randomly. 1. Move IM-angel functionality into a separate file, create Angel class. 2. Be more verbose; 3. Fix typo in FLUSH INSTANCES implementation; 4. Polishing.
-
- 16 Feb, 2007 3 commits
-
-
malff/marcsql@weblab.(none) authored
-
malff/marcsql@weblab.(none) authored
into weblab.(none):/home/marcsql/TREE/mysql-5.0-rt-merge
-
malff/marcsql@weblab.(none) authored
-
- 15 Feb, 2007 2 commits
-
-
malff/marcsql@weblab.(none) authored
into weblab.(none):/home/marcsql/TREE/mysql-5.1-rt-merge
-
Kristofer.Pettersson@naruto. authored
- The condition variable implementation "lost" a signal to WaitOnSingleObject when a semaphore was released. - The signal could be consumed by a new call to pthread_cond_wait before all waiting threads had awoken. - The new implementation of pthread_cond_* uses events instead of semaphores. It also uses an extra lock to protect entry into new cond wait before the broadcast has finished.
-
- 14 Feb, 2007 5 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
igor@olga.mysql.com authored
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt
-
- 13 Feb, 2007 7 commits
-
-
ibabaev@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-opt
-
igor@olga.mysql.com authored
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
ibabaev@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-opt
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug25807/my51-bug25807
-
cmiller@zippy.cornsilk.net authored
Showstopper and regression against 5.0.24. Previously, we ignored seek() errors (see Bug#22828) and let seek()s against pipes fail. Now, since we check that a seek didn't fail, and return without reading, this bug popped up. This restores the behavior for file-ish objects that could never be seek()ed.
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.1-opt
-