From 6222ca41a5066d8dd56d4f4b7aa47d742fd8095e Mon Sep 17 00:00:00 2001
From: "kroki@mysql.com" <>
Date: Fri, 7 Apr 2006 15:30:40 +0400
Subject: Bug#15933: max_used_connections is wrong after FLUSH STATUS if
 connections are cached

After FLUSH STATUS max_used_connections was reset to 0, and haven't
been updated while cached threads were reused, until the moment a new
thread was created.

The first suggested fix from original bug report was implemented:

  a) On flushing the status, set max_used_connections to
  threads_connected, not to 0.

  b) Check if it is necessary to increment max_used_connections when
  taking a thread from the cache as well as when creating new threads
---
 sql/mysql_priv.h | 1 +
 1 file changed, 1 insertion(+)

(limited to 'sql/mysql_priv.h')

diff --git a/sql/mysql_priv.h b/sql/mysql_priv.h
index ca7801039c5..03121383d8a 100644
--- a/sql/mysql_priv.h
+++ b/sql/mysql_priv.h
@@ -1097,6 +1097,7 @@ File open_binlog(IO_CACHE *log, const char *log_file_name,
 
 /* mysqld.cc */
 extern void MYSQLerror(const char*);
+void refresh_status(THD *thd);
 
 /* item_func.cc */
 extern bool check_reserved_words(LEX_STRING *name);
-- 
cgit v1.2.1