Bug #44956 SHOW GLOBAL STATUS reports wrong setting for innodb_have_sync_atomic

• Submitted: 19 May 2009 18:06
• Modified: 20 Jun 2009 19:34
• Reporter: Trudy Pelzer
• Status: No Feedback
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.4.0
• OS: Solaris (SPARC)
• Assigned to: Assigned Account
• CPU Architecture: Any

[19 May 2009 18:06] Trudy Pelzer

Description:
During the beta-test phase of 5.4, a tester saw SHOW GLOBAL STATUS reporting
that innodb_have_sync_atomic was OFF, even though the line:
"InnoDB: Mutex and rw_lock use atomics" 
was written to the Server error log (on T5220 and the M3000 machines).

Richard Smith of the PAE team looked into the report and said:
"I think there's a bug in sql/sql_show.cc. export_vars.innodb_have_sync_atomic
is correctly set to 1, and is defined with type of ibool/ulint (8 bytes)
elsewhere, but the function show_status_array in sql_show.cc treats it as a
bool (1 byte). On big-endian architectures this byte will contain 0, not 1."

How to repeat:
Run the 5.4.0 Solaris 10 SPARC binary and verify the setting of the
innodb_have_sync_atomic variable and log contents.

[20 May 2009 19:34] Sveta Smirnova

Thank you for the report.

I can not repeat described behavior. Please provide your configuration file/options you started mysqld with.

[20 Jun 2009 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".