MySQL Bugs: #35697: Variables do not have a default value on solaris 10

Bug #35697	Variables do not have a default value on solaris 10
Submitted:	31 Mar 2008 9:08	Modified:	30 Apr 2008 10:45
Reporter:	Salman Rawala	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S2 (Serious)
Version:	5.1.22	OS:	Solaris (Sun Solaris 10)
Assigned to:		CPU Architecture:	Any
Tags:	default value, solaris 10, solaris 10 default value, system variable default value

Description:
The following variables cause an error (Error 1230, Variable does not have a default value) on Sun Solaris 10 when setting a default value to them.

innodb_thread_concurrency
innodb_table_locks
innodb_sync_spin_loops
innodb_support_xa
innodb_max_purge_lag
innodb_max_dirty_pages_pct
innodb_flush_log_at_trx_commit
innodb_fast_shutdown
innodb_concurrency_tickets
innodb_commit_concurrency
innodb_autoextend_increment
innodb_thread_sleep_delay

This problem may be with other versions of solaris but for this case the one under consideration is Solaris 10.

The documentation does not specify anything specific to solaris, relating to this scenario.

How to repeat:
SET @@GLOBAL.innodb_thread_concurrency = DEFAULT;
SET @@GLOBAL.innodb_table_locks = DEFAULT;
SET @@GLOBAL.innodb_sync_spin_loops = DEFAULT;
SET @@GLOBAL.innodb_support_xa = DEFAULT;
SET @@GLOBAL.innodb_max_purge_lag = DEFAULT;
SET @@GLOBAL.innodb_max_dirty_pages_pct = DEFAULT;
SET @@GLOBAL.innodb_flush_log_at_trx_commit = DEFAULT;
SET @@GLOBAL.innodb_fast_shutdown = DEFAULT;
SET @@GLOBAL.innodb_concurrency_tickets = DEFAULT;
SET @@GLOBAL.innodb_commit_concurrency = DEFAULT;
SET @@GLOBAL.innodb_autoextend_increment = DEFAULT;
SET @@GLOBAL.innodb_thread_sleep_delay = DEFAULT;

Suggested fix:
The default value should get applied as expected without causing any errors.

Thank you for a problem report. Please, try to repeat with a newer version, 5.1.23, and inform about the results.

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".