Friday, May 3, 2024
1
rated 0 times [  1] [ 0]  / answers: 1 / hits: 5464  / 1 Year ago, thu, february 9, 2023, 2:47:19

I have encountered a weird problem with innodb_buffer_pool_size configuration on 5.5.23-1~dotdeb.0 (Debian):



Whatever new value that I choose in my.cnf for innodb_buffer_pool_size (e.g 3G, 4G, 8000M), after restarting mysql I still get innodb_buffer_pool_size = 128 M.



Values of other my.cnf parameters can be changed without any issue.



I have also checked and have no other my.cnf on the file system other than /etc/mysql/my.dnf. So does this mean that innodb_buffer_pool_size = 128 M is hard-coded at compile time? If so, how can I fix this? If not, what can possibly have caused the problem? Thanks



P.S. I first asked this question at dba forum but people there seem not to have insight about mysql debian package.


More From » configuration

 Answers
1

I needed to put the config WITHIN [mysqld] block in my.cnf to take effect.



more details here


[#39046] Thursday, February 9, 2023, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
ligenvirt

Total Points: 238
Total Questions: 98
Total Answers: 100

Location: Senegal
Member since Fri, Aug 21, 2020
4 Years ago
ligenvirt questions
Tue, Aug 17, 21, 02:28, 3 Years ago
Thu, Sep 23, 21, 17:55, 3 Years ago
Mon, Oct 18, 21, 03:34, 3 Years ago
;