An error occurred fetching the project authors.
- 16 Dec, 2009 1 commit
-
-
Alexander Nozdrin authored
According to new numbering scheme mysql-next-mr does not have its own version. Some version placeholder is used instead. It's been agreed that 5.5.99 will be used as a placeholder.
-
- 02 Dec, 2009 1 commit
-
-
karen.langford@sun.com authored
-
- 25 Nov, 2009 2 commits
-
-
Kent Boortz authored
-
Alexander Nozdrin authored
The following 6.0 revisions were analyzed: - sp1r-brian@zim.(none)-20071228102738-21894 - sp1r-brian@zim.(none)-20071228121841-56447 - sp1r-brian@zim.(none)-20071228205403-56423 - sp1r-brian@zim.(none)-20071228221139-55341 - sp1r-brian@zim.(none)-20071228233443-55352 - sp1r-brian@zim.(none)-20071229094527-61763 - sp1r-brian@zim.(none)-20071230203739-61746 - sp1r-brian@zim.(none)-20080102213805-61741 - sp1r-brian@zim.(none)-20080103201041-61746 - sp1r-brian@zim.(none)-20080104234927-59875 - sp1r-brian@zim.(none)-20080105005827-59874 - sp1r-brian@zim.(none)-20080105012020-59865 - sp1r-brian@zim.(none)-20080106003858-59857 - sp1r-brian@zim.(none)-20080123195552-31680 - sp1r-brian@zim.(none)-20080124201848-29999 - sp1r-brian@zim.(none)-20080129075144-36991 - sp1r-cbell/Chuck@mysql_cab_desk.-20080215041806-21954 - sp1r-vvaintroub@wva.-20080212124547-06272 - sp1r-dfischer/mysqldev@mysql.com/production.mysql.com-20071223184258-15140 - sp1r-brian@zim.(none)-20080206122216-35774 - sp1r-baker@bk-internal.mysql.com-20080209005622-35947 - sp1r-baker@bk-internal.mysql.com-20080224215608-24613 - sp1r-baker@bk-internal.mysql.com-20080307170710-63543 - sp1r-baker@bk-internal.mysql.com-20080312233205-13069 - sp1r-Reggie@core.-20080402175211-28643 - kpettersson@mysql.com-20080901101150-4ne74r8v0492vv42 - alik@sun.com-20090805173811-9fzt0ymcp9tsvn7k - alik@sun.com-20090805173937-fcv1fdveodq5x9gb - alik@sun.com-20090805175009-g1od16i3t1xkw2qr - kostja@sun.com-20090805200643-j9i4fy7ii8ijho5c - alik@sun.com-20090807195303-j4fb5m4l1dgdahwo - alik@sun.com-20090808114848-3rkzr9kifrijzaqy - alik@sun.com-20090810041739-ugmx34h34uid8mox - alik@sun.com-20090810105306-rf43rfyzzblsy5e7 - alik@sun.com-20090810123113-ccdjwai68b5woqdm - alik@sun.com-20090811080423-gb7pibec1znaydzy - alik@sun.com-20090811082130-5uckar1vx3kdsw7g - alik@sun.com-20090812202051-uqkfwwxxcjvo5ean The following bugfixes are also backported within this patch: - Bug#34292: netdb.h missing in hostname.cc - Bug#39153: Failing to lookup a host name can lead to crash in current IPv6 implementation - Bug#38247: Server does not resolve connecting ip's - Bug#43006: main.skip_name_resolve fails on Windows in PB2 - Bug#45606: ACL requires IPv4-mapped addresses to be used - Bug#45584: Host name cache does not work as a cache
-
- 24 Nov, 2009 1 commit
-
-
Marc Alff authored
-
- 23 Nov, 2009 1 commit
-
-
Konstantin Osipov authored
------------------------------------------------------------- revno: 2877 committer: Davi Arnaut <Davi.Arnaut@Sun.COM> branch nick: 35164-6.0 timestamp: Wed 2008-10-15 19:53:18 -0300 message: Bug#35164: Large number of invalid pthread_attr_setschedparam calls Bug#37536: Thread scheduling causes performance degradation at low thread count Bug#12702: Long queries take 100% of CPU and freeze other applications under Windows The problem is that although having threads with different priorities yields marginal improvements [1] in some platforms [2], relying on some statically defined priorities (QUERY_PRIOR and WAIT_PRIOR) to play well (or to work at all) with different scheduling practices and disciplines is, at best, a shot in the dark as the meaning of priority values may change depending on the scheduling policy set for the process. Another problem is that increasing priorities can hurt other concurrent (running on the same hardware) applications (such as AMP) by causing starvation problems as MySQL threads will successively preempt lower priority processes. This can be evidenced by Bug#12702. The solution is to not change the threads priorities and rely on the system scheduler to perform its job. This also enables a system admin to increase or decrease the scheduling priority of the MySQL process, if intended. Furthermore, the internal wrappers and code for changing the priority of threads is being removed as they are now unused and ancient. 1. Due to unintentional side effects. On Solaris this could artificially help benchmarks as calling the priority changing syscall millions of times is more beneficial than the actual setting of the priority. 2. Where it actually works. It has never worked on Linux as the default scheduling policy SCHED_OTHER only accepts the static priority 0.
-
- 21 Nov, 2009 1 commit
-
-
Davi Arnaut authored
-
- 18 Nov, 2009 2 commits
- 12 Nov, 2009 1 commit
-
-
Alexander Nozdrin authored
-
- 09 Nov, 2009 1 commit
-
-
hery.ramilison@sun.com authored
-
- 04 Nov, 2009 1 commit
-
-
hery.ramilison@sun.com authored
-
- 05 Nov, 2009 1 commit
-
-
Davi Arnaut authored
-
- 02 Nov, 2009 1 commit
-
-
Sergei Golubchik authored
(mysql-next-mr backport)
-
- 21 Oct, 2009 1 commit
-
-
Alexander Barkov authored
-
- 13 Oct, 2009 1 commit
-
-
karen.langford@sun.com authored
-
- 09 Oct, 2009 4 commits
-
-
Joerg Bruehe authored
A build "--without-server" fails if using "--with-ssl" (YaSSL) The problem was the lack of directory "extra" in a build which did not include the server.
-
Jon Olav Hauglid authored
"have_profiling" 1) Renamed have_community_features server system variable to have_profiling. 2) Removed eable-community-features configure option and ENABLE_COMMUNITY_FEATURES macro. 3) Removed COMMUNITY_SERVER macro and replaced its usage by ENABLED_PROFILING. Only --enable-profiling is now needed to enable profiling. It was the only existing "community feature", so there was no need for both configure options. Using --enable-community-features will give a warning message since it no longer exists.
-
Alexander Nozdrin authored
-
Alexander Nozdrin authored
-
- 06 Oct, 2009 1 commit
-
-
hery.ramilison@sun.com authored
-
- 30 Sep, 2009 1 commit
-
-
sunanda.menon@sun.com authored
-
- 29 Sep, 2009 1 commit
-
-
Ingo Struewing authored
Backport from 6.0 to 5.1. Only those sync points are included, which are used in debug_sync.test. The Debug Sync Facility allows to place synchronization points in the code: open_tables(...) DEBUG_SYNC(thd, "after_open_tables"); lock_tables(...) When activated, a sync point can - Send a signal and/or - Wait for a signal Nomenclature: - signal: A value of a global variable that persists until overwritten by a new signal. The global variable can also be seen as a "signal post" or "flag mast". Then the signal is what is attached to the "signal post" or "flag mast". - send a signal: Assign the value (the signal) to the global variable ("set a flag") and broadcast a global condition to wake those waiting for a signal. - wait for a signal: Loop over waiting for the global condition until the global value matches the wait-for signal. Please find more information in the top comment in debug_sync.cc or in the worklog entry.
-
- 23 Sep, 2009 1 commit
-
-
Alexander Nozdrin authored
-
- 22 Sep, 2009 2 commits
-
-
timothy.smith@sun.com authored
-
Alexander Nozdrin authored
-
- 17 Sep, 2009 2 commits
-
-
Joerg Bruehe authored
Solaris binary packages should be compiled with '-g0', not '-g' The main fix for this is done in the build tools, but in the sources it affects "configure.in" which sets "DEBUG_CXXFLAGS" to be used in all debug builds.
-
Joerg Bruehe authored
Option "--without-server" still not working in 5.1 The general approach is to make sure that source files which require thread support are only compiled if the build really needs thread support, which means when the server is built or a thread-safe client library. This required several changes: - Make sure the subdirectories "storage/" and "plugin/" are only processed if the server is built, not ifclient-only. - Make the compilation of some modules which inherently require threading depend on thread supportin the build. - Separate the handling of threading in "configure.in" from that of server issues, threading is also needed in a non-server build of a thread-safe client library. Also, "libdbug" must get built even in a client-only build, so "dbug/" must be in the list of client directories. In addition, calls to thread functions in source files which can be built without thread support must use the wrapper functions which handle the non-threaded build. So the modules "client/mysqlimport.c" and "client/mysqlslap.c" must call "my_thread_end()" only via "mysql_thread_end()".
-
- 08 Sep, 2009 1 commit
-
-
hery.ramilison@sun.com authored
-
- 03 Sep, 2009 1 commit
-
-
Jonathan Perkin authored
-
- 26 Aug, 2009 1 commit
-
-
joerg.bruehe@sun.com authored
-
- 12 Aug, 2009 1 commit
-
-
karen.langford@sun.com authored
-
- 11 Aug, 2009 1 commit
-
-
sunanda.menon@sun.com authored
-
- 21 Jul, 2009 1 commit
-
-
timothy.smith@sun.com authored
-
- 13 Jul, 2009 1 commit
-
-
timothy.smith@sun.com authored
-
- 07 Jul, 2009 1 commit
-
-
sunanda.menon@sun.com authored
-
- 25 Jun, 2009 1 commit
-
-
MySQL Build Team authored
-
- 24 Jun, 2009 1 commit
-
-
MySQL Build Team authored
-
- 23 Jun, 2009 1 commit
-
-
MySQL Build Team authored
-
- 22 Jun, 2009 1 commit
-
-
Christoffer Hall authored
A hardcoded use of nm and libc was put into configure.in. This broke cross-compiling and is bad practice. Fitting variables now used.
-