Boolean variable not accepting 'ON' as the value

Bug #1131120 reported by Raghavendra D Prabhu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Hrvoje Matijakovic
5.5
Fix Released
Medium
Hrvoje Matijakovic

Bug Description

According to innodb_buffer_pool_populate, it is a boolean variable.

However, setting it to ON fails,

130221 15:16:36 [Warning] mysqld-debug: ignoring option '--innodb-buffer-pool-populate' due to invalid value 'ON'

Setting it to 1 works.

It may be a documentation bug but since this is a boolean variable, 'ON' should work as well right?

Related branches

summary: - Boolean variable not accepting 'ON' as the valuea
+ Boolean variable not accepting 'ON' as the value
Changed in percona-server:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Hrvoje Matijakovic (hrvojem)
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

This is easy to verify and it contradicts documentation, https://www.percona.com/doc/percona-server/5.5/performance/innodb_numa_support.html#innodb_buffer_pool_populate:

130221 12:12:01 [Warning] /home/openxs/dbs/p5.5/bin/mysqld: ignoring option '--innodb-buffer-pool-populate' due to invalid value 'ON'
130221 12:12:01 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
130221 12:12:01 InnoDB: The InnoDB memory heap is disabled
130221 12:12:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130221 12:12:01 InnoDB: Compressed tables use zlib 1.2.5
130221 12:12:01 InnoDB: Using Linux native AIO
130221 12:12:01 InnoDB: Initializing buffer pool, size = 128.0M
130221 12:12:01 InnoDB: Completed initialization of buffer pool
130221 12:12:01 InnoDB: highest supported file format is Barracuda.
130221 12:12:01 InnoDB: Waiting for the background threads to start
130221 12:12:02 Percona XtraDB (http://www.percona.com) 1.1.8-29.3 started; log sequence number 1597945
130221 12:12:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130221 12:12:03 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130221 12:12:03 [Note] Server socket created on IP: '0.0.0.0'.
130221 12:12:03 [Note] Event Scheduler: Loaded 0 events
130221 12:12:03 [Note] /home/openxs/dbs/p5.5/bin/mysqld: ready for connections.
Version: '5.5.29-valgrind-max-debug' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)

Changed in percona-server:
status: In Progress → Confirmed
Changed in percona-server:
status: Confirmed → In Progress
Changed in percona-server:
status: In Progress → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1319

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.