1. 22 Jun, 2006 1 commit
  2. 21 Jun, 2006 1 commit
  3. 15 Jun, 2006 1 commit
  4. 07 Jun, 2006 1 commit
  5. 31 May, 2006 5 commits
  6. 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
  7. 18 May, 2006 2 commits
  8. 17 May, 2006 4 commits
  9. 16 May, 2006 20 commits
  10. 15 May, 2006 4 commits