diff options
| author | Daniel Black <daniel@linux.vnet.ibm.com> | 2018-03-27 07:55:56 +1100 |
|---|---|---|
| committer | Sergey Vojtovich <svoj@mariadb.org> | 2018-04-03 10:37:20 +0400 |
| commit | 8ffbb825e6a09d3055f46ed4b456573aef5c474c (patch) | |
| tree | bfd9c343b03ead1361e5a75f455ca790fe662e97 /sql/mysqld.cc | |
| parent | 10f6b7001bd7b683c013ae407c2c48793caa3633 (diff) | |
| download | mariadb-git-8ffbb825e6a09d3055f46ed4b456573aef5c474c.tar.gz | |
increase upper value of max_prepared_stmt_count to UINT32_MAX
The upper 1M limit for max_prepared_stmt_count was set over 10 years
ago. It doesn't suite current hardware and a sysbench oltp_read_write
test with 512 threads will hit this limit.
Diffstat (limited to 'sql/mysqld.cc')
| -rw-r--r-- | sql/mysqld.cc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sql/mysqld.cc b/sql/mysqld.cc index 435fb07279f..f9089ed9eb9 100644 --- a/sql/mysqld.cc +++ b/sql/mysqld.cc @@ -532,7 +532,7 @@ bool max_user_connections_checking=0; Limit of the total number of prepared statements in the server. Is necessary to protect the server against out-of-memory attacks. */ -ulong max_prepared_stmt_count; +uint max_prepared_stmt_count; /** Current total number of prepared statements in the server. This number is exact, and therefore may not be equal to the difference between @@ -543,7 +543,7 @@ ulong max_prepared_stmt_count; two different connections, this counts as two distinct prepared statements. */ -ulong prepared_stmt_count=0; +uint prepared_stmt_count=0; ulong thread_id=1L,current_pid; ulong slow_launch_threads = 0; uint sync_binlog_period= 0, sync_relaylog_period= 0, |