An error occurred fetching the project authors.
  1. 28 Sep, 2006 1 commit
  2. 26 Jun, 2006 1 commit
    • ingo@mysql.com's avatar
      Bug#16986 - Deadlock condition with MyISAM tables · d27a15a8
      ingo@mysql.com authored
      Addendum fixes after changing the condition variable
      for the global read lock.
      
      The stress test suite revealed some deadlocks. Some were
      related to the new condition variable (COND_global_read_lock)
      and some were general problems with the global read lock.
      
      It is now necessary to signal COND_global_read_lock whenever 
      COND_refresh is signalled.
      
      We need to wait for the release of a global read lock if one 
      is set before every operation that requires a write lock.
      But we must not wait if we have locked tables by LOCK TABLES.
      After setting a global read lock a thread waits until all
      write locks are released.
      d27a15a8
  3. 20 Jun, 2006 1 commit
    • elliot@mysql.com's avatar
      Applying patch from SergeyV · 37e5ec9f
      elliot@mysql.com authored
      Fixes bug#17264, for alter table on win32 for successfull operation completion
      it is used TL_WRITE(=10) lock instead of TL_WRITE_ALLOW_READ(=6), however here
      in innodb handler TL_WRTIE is lifted to TL_WRITE_ALLOW_WRITE, which causes
      race condition when several clients do alter table simultaneously.
      37e5ec9f
  4. 29 May, 2006 1 commit
    • ingo@mysql.com's avatar
      Bug#19815 - CREATE/RENAME/DROP DATABASE can deadlock on a global read lock · d00441e3
      ingo@mysql.com authored
      The order of acquiring LOCK_mysql_create_db
      and wait_if_global_read_lock() was wrong. It could happen
      that a thread held LOCK_mysql_create_db while waiting for
      the global read lock to be released. The thread with the
      global read lock could try to administrate a database too.
      It would first try to lock LOCK_mysql_create_db and hang...
      
      The check if the current thread has the global read lock
      is done in wait_if_global_read_lock(), which could not be
      reached because of the hang in LOCK_mysql_create_db.
      
      Now I exchanged the order of acquiring LOCK_mysql_create_db
      and wait_if_global_read_lock(). This makes 
      wait_if_global_read_lock() fail with an error message for
      the thread with the global read lock. No deadlock happens.
      d00441e3
  5. 24 May, 2006 1 commit
    • monty@mysql.com's avatar
      More DBUG statements · 9e9ca8b6
      monty@mysql.com authored
      Replaced COND_refresh with COND_global_read_lock becasue of a bug in NTPL threads when using different mutexes as arguments to pthread_cond_wait()
      The original code caused a hang in FLUSH TABLES WITH READ LOCK in some circumstances because pthread_cond_broadcast() was not delivered to other threads.
      This fixes:
      Bug#16986: Deadlock condition with MyISAM tables
      Bug#20048: FLUSH TABLES WITH READ LOCK causes a deadlock
      9e9ca8b6
  6. 28 Jul, 2005 1 commit
  7. 03 Jun, 2005 1 commit
  8. 02 Oct, 2004 1 commit
  9. 04 Mar, 2003 1 commit
  10. 05 Jan, 2003 1 commit
  11. 30 Aug, 2002 1 commit
  12. 08 Oct, 2001 1 commit
    • monty@hundin.mysql.fi's avatar
      Updated manual about embedded version. · 88aff4bf
      monty@hundin.mysql.fi authored
      Speed up column-completion in 'mysql'
      Don't use ISAM if HAVE_ISAM is not defined
      A lot of fixes for the embedded version.  All libraries are now included in libmysqld.a
      Changed arguments to convert_dirname() to make it more general.
      Renamed files in the 'merge' directory to all use a common prefix.
      Don't compile both assembler and C functions on x86
      88aff4bf