1. 26 Oct, 2016 2 commits
  2. 25 Oct, 2016 12 commits
  3. 23 Oct, 2016 1 commit
  4. 22 Oct, 2016 1 commit
    • Vladislav Vaintroub's avatar
      MDEV-11104 Fix client to correctly retrieve current user name on Windows · fb38d264
      Vladislav Vaintroub authored
      Prior to this patch name of the user was  read from environment variable
      USER, with a fallback to 'ODBC', if the environment variable is not set.
      
      The name of the env.variable is incorrect (USERNAME usually contains current
      user's name,  but not USER), which made client to  always determine
      current user as 'ODBC'.
      
      The fix is to use GetUserName() instead.
      fb38d264
  5. 21 Oct, 2016 3 commits
  6. 18 Oct, 2016 1 commit
  7. 17 Oct, 2016 2 commits
  8. 16 Oct, 2016 1 commit
  9. 14 Oct, 2016 4 commits
  10. 13 Oct, 2016 6 commits
  11. 05 Oct, 2016 1 commit
  12. 29 Sep, 2016 2 commits
  13. 28 Sep, 2016 4 commits
    • Robert Golebiowski's avatar
      Bug #24740291: YASSL UPDATE TO 2.4.2 · 5c6169fb
      Robert Golebiowski authored
      5c6169fb
    • Arun Kuruvila's avatar
      Bug#24707666: DEFAULT SETTING FOR SECURE-FILE-PRIV SHOULD BE · 7cb79a65
      Arun Kuruvila authored
                    RESTRICTED IN ALL GA RELEASES
      
      Back port of WL#6782 to 5.5 and 5.6. This also includes
      back port of Bug#20771331, Bug#20741572 and Bug#20770671.
      Bug#24695274 and Bug#24679907 are also handled along with
      this.
      7cb79a65
    • Sergei Petrunia's avatar
    • Sergei Petrunia's avatar
      MDEV-10649: Optimizer sometimes use "index" instead of "range" access for UPDATE · a53f3c6d
      Sergei Petrunia authored
      (Fixing both InnoDB and XtraDB)
      
      Re-opening a TABLE object (after e.g. FLUSH TABLES or open table cache
      eviction) causes ha_innobase to call
      dict_stats_update(DICT_STATS_FETCH_ONLY_IF_NOT_IN_MEMORY).
      
      Inside this call, the following is done:
        dict_stats_empty_table(table);
        dict_stats_copy(table, t);
      
      On the other hand, commands like UPDATE make this call to get the "rows in
      table" statistics in table->stats.records:
      
        ha_innobase->info(HA_STATUS_VARIABLE|HA_STATUS_NO_LOCK)
      
      note the HA_STATUS_NO_LOCK parameter. It means, no locks are taken by
      ::info() If the ::info() call happens between dict_stats_empty_table
      and dict_stats_copy calls, the UPDATE's optimizer will get an estimate
      of table->stats.records=1, which causes it to pick a full table scan,
      which in turn will take a lot of row locks and cause other bad
      consequences.
      a53f3c6d