← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to drizzled/statement/replace_select.cc

  • Committer: Lee Bieber
  • Date: 2010-08-21 22:42:44 UTC
  • mto: (1727.1.1 build)
  • mto: This revision was merged to the branch mainline in revision 1728.
  • Revision ID: lbieber@kalebral-2.local-20100821224244-kh3gmsvi45dlbuu1
https://launchpad.net/bugs/622005
For the feature request (https://blueprints.launchpad.net/drizzle/+spec/limit-maximum-sort-size) 
that is requesting the ability to cap various buffers, we first tried setting the join buffer to 
1 to see how that would affect the test results and expose test results that need to 
sorted (by adding --sorted_result). 

Show diffs side-by-side

added added

removed removed

Lines of Context:
drizzled/statement/replace_select.cc
47
47
 
48
48
  unit->set_limit(select_lex);
49
49
 
50
 
  if (session->wait_if_global_read_lock(false, true))
 
50
  if (wait_if_global_read_lock(session, false, true))
51
51
  {
52
52
    return true;
53
53
  }
96
96
     Release the protection against the global read lock and wake
97
97
     everyone, who might want to set a global read lock.
98
98
   */
99
 
  session->startWaitingGlobalReadLock();
 
99
  start_waiting_global_read_lock(session);
100
100
 
101
101
  return res;
102
102
}