MySQL shouldn't "guess" at the variable names

Bug #371752 reported by Vadim Tkachenko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
OurDelta
New
Undecided
Unassigned
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Won't Fix
Undecided
Unassigned
5.5
Won't Fix
Undecided
Unassigned
5.6
Won't Fix
Low
Unassigned
5.7
Fix Released
Low
Unassigned
Percona patches
Won't Fix
Undecided
Unassigned

Bug Description

(reported by Sheeri K. Cabral )

I did not know how to file a bug report against a Percona build of MySQL (not xtradb, that has a launchpad page...). If there could be a clear place on the Percona Labs page, or the documentation page at http://www.percona.com/docs/wiki/patches:start, that would be helpful.
Anyway, here's the bug. group_concat_max_len for some reason isn't set properly, even when it's explicitly set in the /etc/my.cnf (the default is 1024, and we get these errors no matter what we set the group_concat_max_len value in /etc/my.cnf to):

Version: '5.1.33-percona-log' socket: '/mysql/data/mysql.sock' port: 3306 MySQL Community Server (GPL)
090504 8:26:59 [Warning] option 'group_concat_max_len': unsigned value 0 adjusted to 4

[pythian@db02 avail_mysql]$ grep concat /etc/my.cnf
group_concat_max_len=1024

Please let me know if you need any additional information, or if there's an actual bug tracker that I've missed....

We've also seen this in:
5.0.67-d7-ourdelta-sail44-log
and
5.0.67-percona-highperf-b10-log

Tags: upstream
Revision history for this message
Sheeri K. Cabral (awfief) wrote :

I believe this is actually MySQL's fault:

http://bugs.mysql.com/bug.php?id=45379

The response is:

are you sure this is a bug and not just a confusion. options have always been
recognised by their shortest non-ambiguous versions. "group=mysql" is actually
seen as "group_concat_max_len=mysql".

---------------

which is ridiculous -- if there's confusion, then by definition, it's not "non-ambiguous".

(I'd appreciate it if folks could add a comment to http://bugs.mysql.com/bug.php?id=45379)

Revision history for this message
Stewart Smith (stewart) wrote :

I've moved to percona-server project as percona-patches is long obsolete.

Changed in percona-patches:
status: New → Won't Fix
summary: - group_concat_max_len problem
+ MySQL shouldn't "guess" at the variable names
Changed in percona-server:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
linzuxiong (linzuxiong1988) wrote :

2015-06-29 18:14:22 0 [Warning] Using unique option prefix group instead of group_concat_max_len is deprecated and will be removed in a future release. Please use the full name instead.
2015-06-29 18:14:22 0 [Warning] option 'group_concat_max_len': unsigned value 0 adjusted to 4

2015-06-29 18:14:24 41806 [Warning] 'proxies_priv' entry '@ root@youzan' ignored in --skip-name-resolve mode.
2015-06-29 18:14:24 41806 [Note] /opt/percona-server-5.6.24-72.2/bin/mysqld: ready for connections.

--------------------------------

percona-server 5.6.24-72.2

tags: added: upstream
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-1828

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

Other bug subscribers

Related blueprints

Remote bug watches

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