start error without query_cache_size
Bug #897530 reported by
Vadim Tkachenko
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL patches by Codership |
Fix Released
|
Medium
|
Seppo Jaakola | ||
| 5.1 |
Fix Released
|
Medium
|
Seppo Jaakola | ||
| 5.5 |
Fix Released
|
Medium
|
Seppo Jaakola | ||
Bug Description
If query_cache_size is not specified, mysqld fails to start with error
[ERROR] WSREP: Bad value for *query_cache_size: '16M'. Should be integer.
| description: | updated |
| Changed in codership-mysql: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
| milestone: | none → 5.5.17-22.3 |
| status: | Confirmed → In Progress |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
To post a comment you must log in.
Fixed long long parsing to accept k,K,m,M,g,G suffixes. Checking now also query_cache_type, and bailing out only when QC is about to be active.
Fixes:
wsrep-5.5: http://
wsrep-5.1: http://